Tuesday, January 7, 2020
33 changes · master
Enhancements to existing features
When creating a new bank account from a vendor bill or related accounting document, Odoo now automatically sets the vendor as the account holder when available. This reduces manual data entry and helps avoid mistakes when adding vendor banking details.
Original PR description
Description of the issue/feature this PR addresses: Automatically set the account holder Current behavior before PR: When you click on "Create and Edit" for a bank account related to a vendor you always need to fill in the "Account holder" manually. Desired behavior after PR is merged: As we can create a bank account from the account.move we can directly set the vendor (account holder) if there is one set as this almost always matches.  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds a demo activity type for sending emails with a predefined template in CRM. It helps demonstrate how sales teams can use email templates in their workflow, making demo environments more realistic and easier to understand.
Original PR description
Description of the issue/feature this PR addresses: Task: https://www.odoo.com/web?#id=1887986&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.c45a2f20d6e372fe9ed4095d03a097f5 Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Members app now places membership product settings under a dedicated Membership Products item in the Configuration menu. This makes the navigation consistent with other Odoo apps and easier for users to find.
Original PR description
PURPOSE ======= It is odd that the 'configuration' menu item on the 'Members' app does not unfold on configuration items like in all other apps. Even though there are only membership products to configure, the action should still have its dedicated menu item for consistency across modules. SPECIFICATION ============= 'Move' action membership.action_membership_products to a new 'Membership Products' menu item under 'Members/Configuration' TaskID: 2167683 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Time Off app now includes improved tooltip guidance for the person responsible for time off requests. This helps users better understand the field’s purpose and reduces confusion when configuring employee leave management.
Resolved issues and error corrections
This fixes an empty blank space that appeared in product settings when website sales and event sales were installed together. The product form layout is reorganized so related options appear in the right place, improving clarity without changing business workflows.
Original PR description
Task : https://www.odoo.com/web#id=2150643&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.2eaa5df3bef2cec6d157c5fc41fbd0f5 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Let's assume a many2many_checkboxes widget in a form view with a dynamic domain (depending on another field in the view). At first rendering, the widget contains a checkbox for each value matching the domain. Before this rev., if the user changed the value of the field used in the domain, the many2many_checkboxes wasn't redrawn, so it still displayed the values matching the previous version of the domain. Closes #38509 Closes #40173 Co-authored-by: Aaron Bohy <aab@odoo.com> Des
Original PR description
Let's assume a many2many_checkboxes widget in a form view with a dynamic domain (depending on another field in the view). At first rendering, the widget contains a checkbox for each value matching the domain. Before this rev., if the user changed the value of the field used in the domain, the many2many_checkboxes wasn't redrawn, so it still displayed the values matching the previous version of the domain. Closes #38509 Closes #40173 Co-authored-by: Aaron Bohy <aab@odoo.com> Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42730 Forward-Port-Of: odoo/odoo#42564
Website theme preview images now load correctly even when the Website app is installed from the command line instead of the apps screen. This makes theme selection more consistent for deployments and automated setup processes.
Original PR description
Themes image would not be shown correctly in the theme selection if the `website` module was installed in CLI. Indeed, the code supposed to load the theme images was done in the kanban view during theme selection after installing module through apps screen. Now, this code is encapsulated and called in post_init hook of website. This was also needed for an improvement on `test_themes` module, see odoo/design-themes#195.
This fixes an issue that could prevent a restaurant point of sale session from resuming correctly when the restaurant POS module is installed. The change adds a safer check for missing data so users can continue shop operations without interruption.
Original PR description
This is a followup to the fix made in 99615ff6cc0559f6661001e5493876f2d5b69248. When calling JSON.stringify to undefined, it results to undefined, thus, it is necessary to check if the value is undefined before JSON.parse'ing it. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes an obsolete view adjustment in the Sales Renting module that no longer has any effect. It helps keep the product form configuration cleaner and reduces maintenance risk without changing user-facing rental workflows.
Original PR description
Task : https://www.odoo.com/web#id=2150643&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.2eaa5df3bef2cec6d157c5fc41fbd0f5
Steps to reproduce: Create one product with FIFO and automatic inventory valuation. Purchase product with 10 quantity and cost price 100 and mark shipment as done. Add landed cost for done incoming shipment with 2 cost lines E.g. 1. Freight Charges - 100 2. Duty and Charges - 50 So ideally after first outgoing shipment total cost should get updated in product is (1000 + 100 + 50) / 10 which is 115 The issue is that we increment `remaining_value` on the wrong layer. task-2167659 For
Original PR description
Steps to reproduce: Create one product with FIFO and automatic inventory valuation. Purchase product with 10 quantity and cost price 100 and mark shipment as done. Add landed cost for done incoming shipment with 2 cost lines E.g. 1. Freight Charges - 100 2. Duty and Charges - 50 So ideally after first outgoing shipment total cost should get updated in product is (1000 + 100 + 50) / 10 which is 115 The issue is that we increment `remaining_value` on the wrong layer. task-2167659 Forward-Port-Of: odoo/odoo#42834
Remove "Time Off" permission from a normal user (i.e. Marc Demo) Login in as the user, go to Time Off > Managers (Time Off) > Create Switch user. Traceback will popup. This is caused by the computed field function acquiring empty fields on change so the date_from will be False opw-2166477 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42833 Forward-Port-Of: odoo/odoo#42826
Original PR description
Remove "Time Off" permission from a normal user (i.e. Marc Demo) Login in as the user, go to Time Off > Managers (Time Off) > Create Switch user. Traceback will popup. This is caused by the computed field function acquiring empty fields on change so the date_from will be False opw-2166477 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42833 Forward-Port-Of: odoo/odoo#42826
Make sure `to_date` is not `False` before comparing. opw-2165860 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42839
Original PR description
Make sure `to_date` is not `False` before comparing. opw-2165860 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42839
- Create a customer invoice. - Validate it. - A payment reference (`invoice_payment_ref`) is given. - Refund with option 'Partial Refund' or 'Full Refund' The `invoice_payment_ref` field is kept, so when the refund is validated the same reference is used. The `invoice_payment_ref` field should be cleared so a new one is generated. opw-2159166 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I
Original PR description
- Create a customer invoice. - Validate it. - A payment reference (`invoice_payment_ref`) is given. - Refund with option 'Partial Refund' or 'Full Refund' The `invoice_payment_ref` field is kept, so when the refund is validated the same reference is used. The `invoice_payment_ref` field should be cleared so a new one is generated. opw-2159166 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42819
Before this commit, pointer events were prevented on all checkboxes in readonly list views. That meant that the boolean_toggle widget for instance could not be properly toggled in a non-editable list (which was the purpose of such a widget). Now, pointer events are only disabled if the checkbox is not a widget field, meaning that any widget applied to a boolean will delegate the handling of all events to its widget. This fix cannot be tested as the `pointer-events` property does not af
Original PR description
Before this commit, pointer events were prevented on all checkboxes in readonly list views. That meant that the boolean_toggle widget for instance could not be properly toggled in a non-editable list (which was the purpose of such a widget). Now, pointer events are only disabled if the checkbox is not a widget field, meaning that any widget applied to a boolean will delegate the handling of all events to its widget. This fix cannot be tested as the `pointer-events` property does not affect manual event triggering. Task 2154055 Forward-Port-Of: odoo/odoo#42332
In developer mode, Marketing information fields are shown twice. [Task ID - 2167971](https://www.odoo.com/web?#id=2167971&action=333&active_id=1725&model=project.task&view_type=form&menu_id=4720) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42776
Original PR description
In developer mode, Marketing information fields are shown twice. [Task ID - 2167971](https://www.odoo.com/web?#id=2167971&action=333&active_id=1725&model=project.task&view_type=form&menu_id=4720) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42776
Consider an x2many field with `context={'active_test': False}`. The value of that field should always contain inactive records, as the field's own context overrides the context of the current record. Forward-Port-Of: odoo/odoo#42784
Original PR description
Consider an x2many field with `context={'active_test': False}`. The value of that field should always contain inactive records, as the field's own context overrides the context of the current record.
Forward-Port-Of: odoo/odoo#42784In v12, it was possible to add an internal note on a journal entry. In order to retrieve this feature, we add the field in the 'Other Info' tab. Note that this tab is only displayed for journal entries, not invoices. Therefore, the same field is not displayed twice. opw-2167108 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com
Original PR description
In v12, it was possible to add an internal note on a journal entry. In order to retrieve this feature, we add the field in the 'Other Info' tab. Note that this tab is only displayed for journal entries, not invoices. Therefore, the same field is not displayed twice. opw-2167108 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42813
Since revision cb618e9a99ea3b86fdeed0, `previous_product_uom_qty` is not set in the context anymore but passed as parameter. opw-2146706 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42737
Original PR description
Since revision cb618e9a99ea3b86fdeed0, `previous_product_uom_qty` is not set in the context anymore but passed as parameter. opw-2146706 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42737
- The module `website` instanciate the environment bound to request before `_dispatch` is called. This causes issues with with routes that create their own psycopg2 cursor. To be more precise, the issue that allowed us to discover this instanciation is linked to the module `auth_oauth`. The route `/auth_oauth/signin` is a `none` route that receives a database name. It uses the db name to create a cursor and an environment manually to process the OAuth
Original PR description
- The module `website` instanciate the environment bound to request before `_dispatch` is called. This causes issues with with routes that create their own psycopg2 cursor. To be more precise, the…
- The module `website` instanciate the environment bound to
request before `_dispatch` is called.
This causes issues with with routes that create their own
psycopg2 cursor.
To be more precise, the issue that allowed us to discover this
instanciation is linked to the module `auth_oauth`.
The route `/auth_oauth/signin` is a `none` route that receives
a database name. It uses the db name to create a cursor and
an environment manually to process the OAuth signin, log-in the user
then assume it is safe to now use `request.env` to process the rest
of the code.
But here, since a cursor has already been created in `request` before the
route had the chance to commit its changes to `res.users`, the
changes made in the route `/auth_oauth/signin` are not available.
And this causes issues with the computation of the session token
done in the method `_compute_session_token` in the model `res.users`.
It uses the field `oauth_access_token` to compute the session token.
But since, the cursor in `request` is in a transaction that is not
yet aware of the changes made on this field, it will compute a
session token using the old `oauth_access_token` and store this
outdated token in the client's session.
Then here depending if you are using a multi-worker or a multi-thread
Odoo, you either are never signed in or your session is expired
after a cache cleaning (the method `_compute_session_token` is cached).
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#41866…hase journals When an account of type receivable or payable is used as default debit account or default credit account of a journal of type sale or purchases, an error is raised. Now, constraints are added to avoid this. opw-2151924 Forward-Port-Of: odoo/odoo#42713 Forward-Port-Of: odoo/odoo#41693
Original PR description
…hase journals When an account of type receivable or payable is used as default debit account or default credit account of a journal of type sale or purchases, an error is raised. Now, constraints are added to avoid this. opw-2151924 Forward-Port-Of: odoo/odoo#42713 Forward-Port-Of: odoo/odoo#41693
Closes #29363 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42783
Original PR description
Closes #29363 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42783
- Set USD as company currency - Set the EUR rate to 1.5 - Create a product A: FIFO & automated, invoicing based on delivery - Create a pricelist in EUR - Buy some quantity @ 100 USD - Create a SO for 1 @ 200 EUR - Confirm the SO, validate the picking, generate the invoice - Do not set an invoice date - Post the invoice The COGS are incorrect: Amount Currency Debit Credit Stock Interim (Delivered) 0.00 0.00 66
Original PR description
- Set USD as company currency - Set the EUR rate to 1.5 - Create a product A: FIFO & automated, invoicing based on delivery - Create a pricelist in EUR - Buy some quantity @ 100 USD - Create a SO for…
- Set USD as company currency
- Set the EUR rate to 1.5
- Create a product A: FIFO & automated, invoicing based on delivery
- Create a pricelist in EUR
- Buy some quantity @ 100 USD
- Create a SO for 1 @ 200 EUR
- Confirm the SO, validate the picking, generate the invoice
- Do not set an invoice date
- Post the invoice
The COGS are incorrect:
Amount Currency Debit Credit
Stock Interim (Delivered) 0.00 0.00 66.67
Expense 0.00 66.67 0.00
It should be:
Amount Currency Debit Credit
Stock Interim (Delivered) 0.00 0.00 100.00
Expense 0.00 100.00 0.00
Commit 3a6ada5 attempted to correct the issue, but it was only
working when an invoice date was set.
In the current situation, when no invoice date is set, there is a
conversion issue. This is because of [1], which ultimately calls [2].
This triggers a recomputation of the credit and debit in [3].
After the accounting refactoring, it is assumed that all AML have the
same currency than the AM. This is for the case in [4]. In case of the
COGS, it is not the case.
Note that we could have done the conversion in Amount Currency (see
PR #42646). But that leads to a recomputation of the debit and credit
which (1) is unnecessary and (2) could lead to rounding errors.
[1] https://github.com/odoo/odoo/blob/01a24fd1df32766a9ed6cedd571ed30c75ef726b/addons/account/models/account_move.py#L2079
[2] https://github.com/odoo/odoo/blob/01a24fd1df32766a9ed6cedd571ed30c75ef726b/addons/account/models/account_move.py#L2894
[3] https://github.com/odoo/odoo/blob/01a24fd1df32766a9ed6cedd571ed30c75ef726b/addons/account/models/account_move.py#L2725-L2726
[4] https://github.com/odoo/odoo/blob/f71979a681d95d98db19a80feb59fdf684ec361f/addons/account/models/account_move.py#L337-L339
opw-2148171
opw-2162068
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#42774Create multiple tax and assign them to the same tax group. Now create an invoice, in the line add all the taxes in the group. Save and click on "Preview". In the tax recap the tax group will be reported applied on a total equal to the number of used taxes multiplied by the total of the product. This append because in the calculation the tax are included multiple times and not just once per group. opw-2158989 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.co
Original PR description
Create multiple tax and assign them to the same tax group. Now create an invoice, in the line add all the taxes in the group. Save and click on "Preview". In the tax recap the tax group will be reported applied on a total equal to the number of used taxes multiplied by the total of the product. This append because in the calculation the tax are included multiple times and not just once per group. opw-2158989 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42628 Forward-Port-Of: odoo/odoo#42523
Description of the issue/feature this PR addresses: Fix a typo Follow-up of https://github.com/odoo/odoo/pull/41683 Current behavior before PR: The sentence says "in edit more" instead of "in edit mode" Desired behavior after PR is merged: The sentence says "In edit mode" instead of "in edit more". -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42625
Original PR description
Description of the issue/feature this PR addresses: Fix a typo Follow-up of https://github.com/odoo/odoo/pull/41683 Current behavior before PR: The sentence says "in edit more" instead of "in edit mode" Desired behavior after PR is merged: The sentence says "In edit mode" instead of "in edit more". -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42625
Issue from rim: In runbot 12.3 - Go to Purchase - Create a PO with one product line: qty 1 / unit price 1000 - Validate the PO and create the Invoice => DON'T VALIDATE THE INVOICE YET - Go back to the PO, change the unit price to 2000 - Go back to the invoice, validate it ==> the PO is marked as "fully invoiced" because the qty "1 unit" is counted as "invoiced" => we should not be able to change the price of a line that has a
Original PR description
Issue from rim:
In runbot 12.3
- Go to Purchase
- Create a PO with one product line: qty 1 / unit price 1000
- Validate the PO and create the Invoice
=> DON'T VALIDATE THE INVOICE YET
- Go back to the PO, change the unit price to 2000
- Go back to the invoice, validate it
==> the PO is marked as "fully invoiced" because the qty "1 unit"
is counted as "invoiced"
=> we should not be able to change the price of a line that has
already been invoiced, even in draft
Cause
It seems that in all the PO's invoices state, we can edit a PO line.
No restriction?
Solution
Set the line price column to read only when they have a linked
invoice.
OPW-2161477
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#42758
Forward-Port-Of: odoo/odoo#42583Before this commit, negative numbers are never rendered as human readable (e.g. 34000 -> 34k). TaskID: 2160790 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42739
Original PR description
Before this commit, negative numbers are never rendered as human readable (e.g. 34000 -> 34k). TaskID: 2160790 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42739
Steps to reproduce the bug: - Create a journal entry JE - Add a partner P and an account A - Click on 'Add a line' Bug: A line with P and A was suggested instead of only P as smart suggestion opw:2152827 Forward-Port-Of: odoo/odoo#42497
Original PR description
Steps to reproduce the bug: - Create a journal entry JE - Add a partner P and an account A - Click on 'Add a line' Bug: A line with P and A was suggested instead of only P as smart suggestion opw:2152827 Forward-Port-Of: odoo/odoo#42497
Description of the issue/feature this PR addresses: Resolve XML-RPC error Fixes https://github.com/odoo/odoo/issues/42268 Closes https://github.com/odoo/odoo/pull/42272 Current behavior before PR: If this function is triggered through XML-RPC it will give back None which crashes XML-RPC unless you've activated allow_none Desired behavior after PR is merged: By returning a value the function will work fine through XML-RPC even with allow_none not activated. -- I confirm I have s
Original PR description
Description of the issue/feature this PR addresses: Resolve XML-RPC error Fixes https://github.com/odoo/odoo/issues/42268 Closes https://github.com/odoo/odoo/pull/42272 Current behavior before PR: If this function is triggered through XML-RPC it will give back None which crashes XML-RPC unless you've activated allow_none Desired behavior after PR is merged: By returning a value the function will work fine through XML-RPC even with allow_none not activated. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42752
The quantity values are the quantities by day and therefore renamed as "Daily * Qty". Also, change the default measure of the pivot view to highlight that in a cleaner way. Forward-Port-Of: odoo/enterprise#7583 Forward-Port-Of: odoo/enterprise#7342
Original PR description
The quantity values are the quantities by day and therefore renamed as "Daily * Qty". Also, change the default measure of the pivot view to highlight that in a cleaner way. Forward-Port-Of: odoo/enterprise#7583 Forward-Port-Of: odoo/enterprise#7342
…esh too fast Don't show error when trying to manually refresh and it results in an error saying that we already initiated a refresh not too long ago. Prevent Deadlock in some case: Deadlock could appear in the following case: call to _ponto_fetch that will result in an error because access token has expired, in that case we generate a new access token (which will write the new access token to the record) and then we call back the original route again to retry. This new call can result
Original PR description
…esh too fast Don't show error when trying to manually refresh and it results in an error saying that we already initiated a refresh not too long ago. Prevent Deadlock in some case: Deadlock could appear in the following case: call to _ponto_fetch that will result in an error because access token has expired, in that case we generate a new access token (which will write the new access token to the record) and then we call back the original route again to retry. This new call can result in en error which we have to log to the record as well as raise it for the user to see (we log it to the record because it can happen in a cron as well). Therefore we have a conflict as we already wrote some value on the record for the new access token and we try to write on the same record within a new cursor to say that its status should be changed to FAILED hence a deadlock. Forward-Port-Of: odoo/enterprise#7567
The contract being no longer in today's date (since reaching year 2020) made it so the `test_resource_leave_different_calendars` from `hr_work_entry_holidays/tests/test_leave.py` would fail as it doesn't create a leave for the contract. Forward-Port-Of: odoo/enterprise#7556
Original PR description
The contract being no longer in today's date (since reaching year 2020) made it so the `test_resource_leave_different_calendars` from `hr_work_entry_holidays/tests/test_leave.py` would fail as it doesn't create a leave for the contract. Forward-Port-Of: odoo/enterprise#7556
- Create a kit product, e.g. 1 unit of A is made of 2 units of B - Create a service product with 'Service Tracking' set as 'Create a task in an existing project'. The project must be a 'Field Service' project. - Create a SO with both products, validate => A task is created A picknig for 1 unit of B is created - Go to Field Service, open the task created and 'Mark As Done' The picking is validated with 2 units of B instead of 1. This is because the `_get_qty_procurement` is n
Original PR description
- Create a kit product, e.g. 1 unit of A is made of 2 units of B - Create a service product with 'Service Tracking' set as 'Create a task in an existing project'. The project must be a 'Field Service' project. - Create a SO with both products, validate => A task is created A picknig for 1 unit of B is created - Go to Field Service, open the task created and 'Mark As Done' The picking is validated with 2 units of B instead of 1. This is because the `_get_qty_procurement` is not called with the current product quantity set on the SO lines. Therefore, zero is returned and the quantities are added a second time. opw-2146706 Forward-Port-Of: odoo/enterprise#7544 Forward-Port-Of: odoo/enterprise#7537
…e and purchase journals opw-2151924 Forward-Port-Of: odoo/enterprise#7528 Forward-Port-Of: odoo/enterprise#7522
Original PR description
…e and purchase journals opw-2151924 Forward-Port-Of: odoo/enterprise#7528 Forward-Port-Of: odoo/enterprise#7522