Merge lp:~openerp-dev/openobject-addons/6.1-opw-575797-odo into lp:openobject-addons/6.1
Status: | Work in progress | ||||
---|---|---|---|---|---|
Proposed branch: | lp:~openerp-dev/openobject-addons/6.1-opw-575797-odo | ||||
Merge into: | lp:openobject-addons/6.1 | ||||
Diff against target: |
168 lines (+63/-10) (has conflicts) 3 files modified
project/project.py (+9/-2) project_long_term/project_long_term.py (+17/-5) resource/resource.py (+37/-3) Text conflict in resource/resource.py |
||||
To merge this branch: | bzr merge lp:~openerp-dev/openobject-addons/6.1-opw-575797-odo | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Raphael Collet (OpenERP) | Pending | ||
Review via email:
|
Description of the change
[FIX] OPW 575797: resource,project: fix erroneous scheduling due to timezone issues
The phases and tasks scheduling is based on the
working time specification, which only contains
days of week and start-stop hours. It only makes
sense when taken in the timezone of the user,
not the server-side timezone (always UTC).
The scheduling is more intuitive if we avoid
to compute it on UTC-converted hours (which
would give very strange working hours in some
places, like 23PM-8AM). Therefore to avoid
more mistakes we convert the constraint timestamps
to the user timezone before scheduling tasks
and phases, and then back to UTC when storing
the computed result
Unmerged revisions
- 6851. By Olivier Dony (Odoo)
-
[FIX] OPW 575797: resource,project: fix erroneous scheduling due to timezone issues
The phases and tasks scheduling is based on the
working time specification, which only contains
days of week and start-stop hours. It only makes
sense when taken in the timezone of the user,
not the server-side timezone (always UTC).
The scheduling is more intuitive if we avoid
to compute it on UTC-converted hours (which
would give very strange working hours in some
places, like 23PM-8AM). Therefore to avoid
more mistakes we convert the constraint timestamps
to the user timezone before scheduling tasks
and phases, and then back to UTC when storing
the computed result
See also related bug 932584