diff options
| author | jem-odoo <jem@openerp.com> | 2018-09-10 15:06:53 +0200 |
|---|---|---|
| committer | jem-odoo <jem@openerp.com> | 2018-09-13 14:44:35 +0200 |
| commit | 64adff43d8fcea9e44a7a42008cd6d8f470839ac (patch) | |
| tree | 38de98cd0aef3a2e00e80cbfc0ec673f11b324c4 /addons/web/static/src | |
| parent | ecc8ff826083d3c157b268ff03221bbee5e390e4 (diff) | |
[REF] sale_timesheet: make project billable wizard
When introducing the 'employee rate' mode to timesheet
on project, we break the wizard: its goal was to link the
existing timesheets to the SO line in order to invoice them.
(Employee rate commit: b4af54f9c23b65abe50dde3dfb397510ec2fcee4)
This commit makes the wizard compatible with the employee rate
feature, without breaking invoicing at task rate flow.
Two possible flows, starting with a non billable project:
* project rate: the wizard will create a SO with one SOL,
and will link the task without SOL set to the new one.
The project will also be linked to that SOL.
* employee rate: the user has to fill a map to associate
product and employee. If the same product is set 2 times
with the same price (and so, 2 different employees), only
one SOL will be created on the SO. When submitting, the
project map will be filled and the project will be linked
to the SO. No fallback SOL will be set on project or on
the tasks.
Both use cases will be stopped if a timesheet of the project's
tasks is already linked to a sale line. If not, the timesheets
will be associated to the correct SOL (dependning of the billable
type), and the delivered quantity will be incremented, making
the SO invoicable. The tasks'customer will also be set.
Future work: setting a product per task (which will be a real
'task rate' feature).
Task #1883640
Diffstat (limited to 'addons/web/static/src')
0 files changed, 0 insertions, 0 deletions
