Merge lp:~openerp-dev/openobject-addons/7.0-opw-605218-ado into lp:openobject-addons/7.0
Status: | Superseded |
---|---|
Proposed branch: | lp:~openerp-dev/openobject-addons/7.0-opw-605218-ado |
Merge into: | lp:openobject-addons/7.0 |
Diff against target: |
29 lines (+13/-0) 1 file modified
project/project.py (+13/-0) |
To merge this branch: | bzr merge lp:~openerp-dev/openobject-addons/7.0-opw-605218-ado |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Amit Dodiya (OpenERP) (community) | Needs Resubmitting | ||
Denis Ledoux (OpenERP) | Disapprove | ||
Naresh(OpenERP) | Pending | ||
Review via email: mp+212089@code.launchpad.net |
This proposal has been superseded by a proposal from 2014-03-31.
Description of the change
Hello,
[FIX] project: users are able to create tasks on closed project and also able to see the closed project on dropdown list(of project) on task form
1st Issue - User is able to search the closed project on many2one dropdown on task form:
Steps:
1). Create a new project(for e.g: test), cancel it
2). Now create a task from task menu and type test on many2one field of project
You will find the closed project on list
2nd Issue - User is able to create task from closed project by opening tasks menu from Tasks button on project form:
Steps:
1). Create a new project(for e.g: test), cancel it
2). Now you have tasks button on project, click on it and try to create task
You will see the task is created from that closed project
Regards,
Amit Dodiya
While it seems indeed right to not attach tasks to closed projects, you should not prevent totally user to do so.
In a general matter, we have to keep OpenERP as generic as possible, and this is possible that some users want to be able to attach tasks to closed projects.
Nevertheless, you can help them to avoid doing this mistake by adding a domain on the project field on the tasks view. One line patch.