summaryrefslogtreecommitdiff
path: root/doc/reference/javascript_reference.rst
diff options
context:
space:
mode:
authorXavier BOL (xbo) <xbo@odoo.com>2020-12-04 10:47:04 +0100
committerXavier BOL (xbo) <xbo@odoo.com>2020-12-21 15:17:08 +0100
commit68f72c6db5dbe10b7f1ee42dd149db2d9dd978fc (patch)
treec188eec96a5408b9dbfc067dee2217d58acb1c65 /doc/reference/javascript_reference.rst
parent527d854a4b8b71b5f38d524766834ea5124e9093 (diff)
[FIX] sale_timesheet: determine the correct SOL for timesheet
Before this commit, when we have not any task in timesheet and the projet has not any sale_line_id, the mapping for the project configured as employee rate is not done and return an empty sale order line for the timesheet. Moreover, if we have a task, the project of this task can be different of the project of the timesheet. That's why, the sale order line determined from the project of the task is not a good idea and thus the python constrains called _check_sale_line_in_project_map can be not satisfied. In this commit, we change the condition when there is not task in the timesheet to get the correct sale order line when pricing type of the project is "employee rate". And we now use the project of the timesheet to have the correct SOL for the timesheet. task-2409761
Diffstat (limited to 'doc/reference/javascript_reference.rst')
0 files changed, 0 insertions, 0 deletions