diff options
| author | Yannick Tivisse <yti@odoo.com> | 2017-08-07 12:34:55 +0200 |
|---|---|---|
| committer | Yannick Tivisse <yti@odoo.com> | 2017-08-07 12:34:55 +0200 |
| commit | 623ea432681a8a0861fec6db0194f3911429efb2 (patch) | |
| tree | f97d9b9281ddbdc0fdcd94b1635c08264e64ea6e /odoo/tools/sql.py | |
| parent | cdae67f03a98946a6d313ac6a0b264ae5d8df3c0 (diff) | |
| parent | f8a1e9f6e7090a36b58b5e9a10950d8b6dcc80b2 (diff) | |
[IMP] project: Merge tasks and issues
Purpose
=======
Advantages :
~~~~~~~~~~~~
- using tasks and issues in a project is not easy. Indeed stages are shared but the process is rarely exactly the same. That's why we have a project for master bugs in our prod.
- having tasks and issues causes issues with email templates (it is easy to put a task-related template on an issue-related stage and that may cause crashes) and rating (same here)
- views are globally the same
- using tasks and issues causes issues with mail alias, as you can create only one of them. We have some strange onchange to ensure the alias creates the right model but I don't think it is really user friendly
- code is globally the same between task and issue and therefore will cut the code in half for those models
- timesheeting on issues is not as complete as timesheeting on tasks, and merging them makes sure we have only one way of working with timesheets in project
- customer portal can be simplified as we have only one menu item for project, leading to code reduction and portal simplification
Diffstat (limited to 'odoo/tools/sql.py')
0 files changed, 0 insertions, 0 deletions