diff options
| author | jem-odoo <jem@openerp.com> | 2018-07-10 14:40:32 +0200 |
|---|---|---|
| committer | jem-odoo <jem@openerp.com> | 2018-08-13 17:32:22 +0200 |
| commit | 20cc64f79ea00cf82242fb0cc6c28c6979928ef3 (patch) | |
| tree | ea06fd6c792ebb0115e7ae58adeec10a82228a9a /addons/web_editor/static/src/xml | |
| parent | 02d565cc0edc266c50dc34e6d7e97432d55f9a3f (diff) | |
[IMP] *_timesheet: don't modify past timesheet when transfering task
Impacted modules: hr_timesheet, sale_timesheet
When task is changing project or sale order line, we
don't want anymore to change the linked timesheet.
We now consider a timesheet is done in a specific time
at certain condition that does not have to change when
the environment is modified afterwards.
So, a timesheet linked to an analytic account for a
certain project on a task (and mybe linked to a SO line)
will still be linked to the same object if the task is
billed with another SO or move into a new project.
The idea is task actual configuration (project, AA, SO
line) are the default value at timesheet creation. As
consequences, timesheet from another project can be linked
to a task that does not belong to that project.
Project and task can be modified thougth the UI of timesheet
app. SO line and analytic account of a timesheet can not
be modified as they are more sensitive field (in a business
point of view), especially for invoiced timesheets.
This commit revert opw-1803811, as at that time the
'inheritS' between project and AA was still effective,
and there was only one billable type (task rate) for
task. The introduction of 'employee rate' billing type
will complicate timesheet transfert.
Tasks #34703
Diffstat (limited to 'addons/web_editor/static/src/xml')
0 files changed, 0 insertions, 0 deletions
