Daily updates from Odoo
Navigate
Branch
Tuesday, February 11, 2020
42 changes
Enhancements to existing features
This update tidies up code across accounting, sales, and coupon features, including a more efficient way to cancel coupons in batches. It also reorganizes intrastat-related logic to keep financial and sales reporting functionality easier to maintain, with minimal expected impact on day-to-day users.
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editors now see clearer labels, wider input fields, and publishing controls that work better on mobile. New pages and related website content such as events, jobs, courses, and blogs also have tracking enabled automatically, reducing manual setup for teams.
Original PR description
Description of the issue/feature this PR addresses: TaskID: https://www.odoo.com/web?#id=2088546&action=327&model=project.task&view_type=form&menu_id=4720 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
This update streamlines the setup flow for server actions and tidies related automatic field update behavior. It should make configuration screens behave more consistently with less manual correction for users.
Original PR description
* Server Actions creation flow improved (with context in the views). * Cleanup onchanges * Related readonly updated through onchanges -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update cleans up internal setup data references across several Odoo apps so they can be loaded more directly. It avoids unnecessary processing during data loading, providing a small efficiency improvement without changing user-facing behavior.
Original PR description
`<field name="fname" eval="ref('xml_id'"/>` gives the same result `<field name="fname" ref="xml_id"/>` whereas the latter avoids a useless safe_eval call to evaluate code content.
Those occurrences of the former are therefore replaced by the latter in the existing codebase.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prHelpdesk users can now send coupons by email even when they do not normally have permission to edit coupon records. This ensures the coupon is correctly marked as sent, reducing workflow blockers for customer support teams.
Original PR description
Purpose ======= Helpdesk users don't have the right to write on a coupon. When sending a coupon by email, the coupon is marked as 'sent'. Allow users to send coupons by executing the state change in sudo. TaskID: 2179609 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
VAT number validation has been updated to rely on a maintained standard library instead of an outdated dependency. This improves long-term reliability for customer and company tax ID checks and keeps packaging requirements aligned across supported platforms.
Original PR description
Python module vatnumber doesn't seem maintained anymore. Therefore, we should:
- call directly stdnum (which is maintained and mostly used everywhere in vatnumber)
Also improve stdnum import, vat fix method and vat expected formats
task-1915371
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThe purchase quotations setup now keeps only the active context setting instead of a duplicate unused one. This minor cleanup reduces configuration ambiguity without changing how users create or manage purchase quotations.
Original PR description
Description of the issue/feature this PR addresses: Two context keys
Current behavior before PR: The purchase_rfq action had two context keys defined. One being empty {} and one with quotation_only set to True.
Desired behavior after PR is merged:
There is just one context (the one that is actually used and applied) on the action.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update cleans up how internal setup and demo records reference existing data across several Odoo Enterprise apps. It reduces unnecessary processing when loading those records, with no expected change to day-to-day user workflows.
Original PR description
Enterprise counterpart of https://github.com/odoo/odoo/pull/44883
The website configuration screens for calendar and enterprise features now use clearer wording, making setup options easier to understand. Tracking is also enabled by default, helping businesses collect visitor insights without extra configuration.
Original PR description
TaskID: https://www.odoo.com/web?#id=2088546&action=327&model=project.task&view_type=form&menu_id=4720
The product selection screen now keeps the quantity controls visible and visually disables actions that are not available, such as reducing a quantity that is already zero. This helps users understand how to add products from the field service sales flow and reduces confusion during onboarding.
Original PR description
PURPOSE Many users are confused when they reach the Products kanban view from the 'Add products' stat button and don't understand what they are expected to do. This task aims at improving the onboarding. SPECIFICATIONS Currently, the -/+ buttons were not muted in both the cases, when qty=0 and qty>0. The behaviour is confusing to the user. In order to solve the issue, '-' symbol should has been muted and '+' symbol is clickable if qty=0 and if the qty>1 than both symbols are be clickable. LINKS PR #8256 Task 2170719
Helpdesk teams can now generate coupons directly and send them to customers. This makes it easier for support staff to offer goodwill gestures or compensation without needing another team to create the coupon.
Original PR description
Now an helpdesk user can generate coupon and send it to customer. TaskID: 2179609
Resolved issues and error corrections
The website live chat input box now uses the intended styling instead of appearing as a plain text area. This improves the customer-facing chat experience and makes the live chat widget look consistent with the rest of the site.
Original PR description
### Issue - Install Website Live Chat - Go on your website - Open livechat The composer is a simple textarea without any style. ### Cause According to the code, the initial idea was to re-use the already existing CSS code for the chatter composer. But it is not the case, because there are missing css files and the structure is incorrect. ### Solution Import the CSS files, fix the structure and add a new class "o_customer_composer" to add styles only to this composer. (e.g. the height, because in the chatter composer, it's computed by the JS) **OPW-2179519** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Features or functions removed from Odoo
This update removes leftover code for customizable out-of-office messages that were no longer available for users to set. It simplifies the mail and time-off experience by eliminating obsolete behavior and reducing maintenance risk.
Original PR description
The customizable "out of office" text was removed from the editable views as part of task-2053585, but some places in the code were still using it, even though it was never set anymore. This commit removes the obsolete code. Part of task-2171864
Code cleanup and technical improvements
Odoo removed an underused setting that automatically added user signatures to email templates because it could create confusing or duplicate signatures. Templates that still need a signature now include it directly, making email content clearer and more predictable for users.
Original PR description
The field user_signature wasn't used that much and when used it caused some issues so it has been removed. Existing templates that had the user_signature field set to True were modified to include the user.signature. task-2089252 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo removed an email template setting that automatically appended the sender's signature because it could create confusing or duplicate signatures in some sending flows. Templates that should include a signature now define it directly, making email content more predictable for customer communications.
Original PR description
The field user_signature wasn't used that much and when used it caused some issues so it has been removed. task-2089252 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Intrastat-related logic has been reorganized into dedicated accounting and sales Intrastat modules. This keeps the core accounting and sales areas cleaner while preserving the reporting capabilities businesses use for cross-border trade declarations.
Original PR description
Linked to https://github.com/odoo/odoo/pull/44858
Miscellaneous changes
Before this patch, validating an unreserved move of a dozen while 12 units were reserved resulted in a quant with 0 unit as quantity and 11 units as reserved quantity. Forward-Port-Of: odoo/odoo#45121 Forward-Port-Of: odoo/odoo#45062
Original PR description
Before this patch, validating an unreserved move of a dozen while 12 units were reserved resulted in a quant with 0 unit as quantity and 11 units as reserved quantity. Forward-Port-Of: odoo/odoo#45121 Forward-Port-Of: odoo/odoo#45062
[1] transformed the button to be `a` instead of `button` for validation reasons however `header` only renders `button` tags so the chat button was not visible anymore. [1] eb2f0aabcfd8c3764f7bca1c99448dadc266727e Forward-Port-Of: odoo/odoo#45070
Original PR description
[1] transformed the button to be `a` instead of `button` for validation reasons however `header` only renders `button` tags so the chat button was not visible anymore. [1] eb2f0aabcfd8c3764f7bca1c99448dadc266727e Forward-Port-Of: odoo/odoo#45070
slideshow was having some options shared with the carousel since this PR: https://github.com/odoo/odoo/pull/38997 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45079 Forward-Port-Of: odoo/odoo#44495
Original PR description
slideshow was having some options shared with the carousel since this PR: https://github.com/odoo/odoo/pull/38997 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45079 Forward-Port-Of: odoo/odoo#44495
* = website_hr_recruitment, website_sale It is now possible to change the position of the submit button via the left panel. task-2191409 Forward-Port-Of: odoo/odoo#44907
Original PR description
* = website_hr_recruitment, website_sale It is now possible to change the position of the submit button via the left panel. task-2191409 Forward-Port-Of: odoo/odoo#44907
The for loop will crash when self contains multiple records (on `total` field access) Finetuning of https://github.com/odoo/odoo/commit/733fb360d25f885bd5c5b4688bbbc7f306f6f648 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44010
Original PR description
The for loop will crash when self contains multiple records (on `total` field access) Finetuning of https://github.com/odoo/odoo/commit/733fb360d25f885bd5c5b4688bbbc7f306f6f648 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44010
Before that, depending on rounding errors on floats, it was possible to end up with a matched percentage of 0.999999999 instead of 1.0 on an account move in case of full reconciliation. This could in turn cause problems with cash basis taxes, when checking what proportion of the move is reconciled. Forward-Port-Of: odoo/odoo#44845 Forward-Port-Of: odoo/odoo#44712
Original PR description
Before that, depending on rounding errors on floats, it was possible to end up with a matched percentage of 0.999999999 instead of 1.0 on an account move in case of full reconciliation. This could in turn cause problems with cash basis taxes, when checking what proportion of the move is reconciled. Forward-Port-Of: odoo/odoo#44845 Forward-Port-Of: odoo/odoo#44712
This is a followup of 1d553eea7b4d2ea74e6a5014b0a08930552200ad. Systematically logging import tracebacks can fill up log files, and waste disk space. We therefore log those tracebacks in DEBUG mode, so that they can be activated only when needed. Forward-Port-Of: odoo/odoo#45049 Forward-Port-Of: odoo/odoo#44937
Original PR description
This is a followup of 1d553eea7b4d2ea74e6a5014b0a08930552200ad. Systematically logging import tracebacks can fill up log files, and waste disk space. We therefore log those tracebacks in DEBUG mode, so that they can be activated only when needed. Forward-Port-Of: odoo/odoo#45049 Forward-Port-Of: odoo/odoo#44937
Assume a situation where you trigger a method which is going to create a nested picking with move_lines included and having a filter set which means that your context includes `{'default_product_id': 20}` ```python { 'location_dest_id': 9, 'location_id': 19, 'move_lines': [(0, 0, {'location_dest_id': 1, 'location_id': 2, 'name': u'name', 'partner_id': 1, 'product_id': 10,
Original PR description
Assume a situation where you trigger a method which is going to create a nested picking with move_lines included and having a filter set which means that your context includes `{'default_product_id':…
Assume a situation where you trigger a method which is going to create a
nested picking with move_lines included and having a filter set which
means that your context includes `{'default_product_id': 20}`
```python
{
'location_dest_id': 9,
'location_id': 19,
'move_lines': [(0,
0,
{'location_dest_id': 1,
'location_id': 2,
'name': u'name',
'partner_id': 1,
'product_id': 10,
'product_uom': 1,
'product_uom_qty': 1.0})],
'origin': u'Origin',
'partner_id': 1,
'picking_type_id': 59
}
```
Before the creation of the objects it will inject the default product in
the top level of the dict which should create a picking with one or more
move_lines.
Based on this this injection will overwrite all `product_id` values of the
created move lines as the picking is created last and the default value
will write ALL move lines with this specific product from the context.
**Description of the issue/feature this PR addresses:**
Magic issues with related fields on creation...
No need to write at any time the related field from `stock.picking`
**Current behavior before PR:**
Related field does write on creation all nested move lines with a `default_product_id` from filter context.
**Desired behavior after PR is merged:**
No influence from a simple search filter on creation of records
@nim-odoo @sle-odoo @amoyaux @rco-odoo
I guess you all might be all interested in this case. The fix is simple in this case, but I guess Raphael might have to think about the default injection by a related field for a nested many2many or one2many field in create.
Info: @wt-io-it
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#44989
Forward-Port-Of: odoo/odoo#44916### Issue - Deactivate demo data - Install several modules (e.g. Sales, Helpdesk) - Go on Home - Hard refresh All tours' tips are shown ### Cause In 02dab5d, we wait the DOM to be ready. The DOM wasn't ready in previous version, this is why it seems to work. As the DOM is ready, in check_for_tooltip we have a visible trigger so trigerred = true and the tip is activated. If you activate the debug mode, the DOM is not ready too, this is why it works fine in
Original PR description
### Issue - Deactivate demo data - Install several modules (e.g. Sales, Helpdesk) - Go on Home - Hard refresh All tours' tips are shown ### Cause In 02dab5d, we wait the DOM to be ready. The DOM wasn't ready in previous version, this is why it seems to work. As the DOM is ready, in check_for_tooltip we have a visible trigger so trigerred = true and the tip is activated. If you activate the debug mode, the DOM is not ready too, this is why it works fine in debug mode. https://imgur.com/a/nD8rnl1 ### Solution I don't think that not waiting the DOM to be ready is good so I think we should keep that and handle the case when we update the tours from the _register method. So that, we use the else part of the update method which will break after a tip has been activated. OPW-2188525 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44630
[FIRST ISSUE] Steps to reproduce the bug: - Create a pricelist PL with 50% reduction on all products. - Create a SO with PL - Add an optional product P Bug: The price is correct for P but the discount displayed was 0%. [SECOND ISSUE] Steps to reproduce the bug: - Add the option line to the order Bug: A new line was create for P in the SO with the correct price but the discount was not displayed PS: The discount field on the model sale.order.option has been imple
Original PR description
[FIRST ISSUE] Steps to reproduce the bug: - Create a pricelist PL with 50% reduction on all products. - Create a SO with PL - Add an optional product P Bug: The price is correct for P but the discount displayed was 0%. [SECOND ISSUE] Steps to reproduce the bug: - Add the option line to the order Bug: A new line was create for P in the SO with the correct price but the discount was not displayed PS: The discount field on the model sale.order.option has been implemented to add a new discount to the displayed price unit of the option. But it has not been implemented to show the discount computed with the pricelist. opw:2186470 Forward-Port-Of: odoo/odoo#44985 Forward-Port-Of: odoo/odoo#44703
- Activate variants and pricelists - Go to Product > Products Variants - Search for anything on the 'Pricelist' filter A traceback is raised: 'Can only create cache keys from hashable values...'. This comes from the following change: https://github.com/odoo/odoo/blob/4b06fe19fa68255b7982d15e5847da2f6d6209fd/addons/web/static/src/js/views/control_panel/control_panel_model.js#L962 It returns a list instead of a string. Since a list is not hashable, it causes the issue. We conver
Original PR description
- Activate variants and pricelists - Go to Product > Products Variants - Search for anything on the 'Pricelist' filter A traceback is raised: 'Can only create cache keys from hashable values...'. This comes from the following change: https://github.com/odoo/odoo/blob/4b06fe19fa68255b7982d15e5847da2f6d6209fd/addons/web/static/src/js/views/control_panel/control_panel_model.js#L962 It returns a list instead of a string. Since a list is not hashable, it causes the issue. We convert the value to a tuple, and moreover take the first element of the list. The price computed on 2 pricelists doesn't make sense anyway. opw-2187757 Forward-Port-Of: odoo/odoo#45047 Forward-Port-Of: odoo/odoo#44775
Go to Accounting / Reporting / Management / Invoices Select Pivot view Add "Total" measure expand results adding "invoice #" and product Total will be incorrect because it is summing up the value reported from several lines of the query in which the total is taken as the invoice total, so it will display total * # lines. Using the price retrieved from the single lines fix the issue -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Por
Original PR description
Go to Accounting / Reporting / Management / Invoices Select Pivot view Add "Total" measure expand results adding "invoice #" and product Total will be incorrect because it is summing up the value reported from several lines of the query in which the total is taken as the invoice total, so it will display total * # lines. Using the price retrieved from the single lines fix the issue -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#44654
Forward-Port-Of: odoo/odoo#44548
Original PR description
Forward-Port-Of: odoo/odoo#44548
When adding a custom field, the ORM also adds it to all the models that are inherits'ed, but with the state `base`. BUT dependencies are enforced for `base` fields while they can be ignored for `manual` ones. If the dependencies are also custom fields, depending on the loading order, dependency validation may crash. We avoid enforcing dependency check on fields inherits'ed from custom fields. opw-[2191114](https://www.odoo.com/web?debug=1#id=2191124&action=3531&model=project.task&vie
Original PR description
When adding a custom field, the ORM also adds it to all the models that are inherits'ed, but with the state `base`. BUT dependencies are enforced for `base` fields while they can be ignored for `manual` ones. If the dependencies are also custom fields, depending on the loading order, dependency validation may crash. We avoid enforcing dependency check on fields inherits'ed from custom fields. opw-[2191114](https://www.odoo.com/web?debug=1#id=2191124&action=3531&model=project.task&view_type=form&menu_id=4720) Forward-Port-Of: odoo/odoo#44966 Forward-Port-Of: odoo/odoo#44707
Steps to reproduce: - have Odoo with Dutch language and install Belgian accounting - print "Periodieke BTW aangiften" report - the report is wrongly translated see this document for reference: https://financien.belgium.be/sites/default/files/downloads/165-625-richtlijnen-2016.pdf%22 related pr: https://github.com/odoo/enterprise/pull/8233 opw-2176688 Forward-Port-Of: odoo/odoo#44971
Original PR description
Steps to reproduce: - have Odoo with Dutch language and install Belgian accounting - print "Periodieke BTW aangiften" report - the report is wrongly translated see this document for reference: https://financien.belgium.be/sites/default/files/downloads/165-625-richtlijnen-2016.pdf%22 related pr: https://github.com/odoo/enterprise/pull/8233 opw-2176688 Forward-Port-Of: odoo/odoo#44971
The translation alert dialog was attached to the entire view in case no status bar was found. This resulted in the following layout on large screens: chrome -------------------------------------- | alert dialog | form view | chatter | | | | | -------------------------------------- Whereas when a status bar was set on the form view, the rendering was as follow: chrome -------------------------------------- | s
Original PR description
The translation alert dialog was attached to the entire view in case no status bar was found. This resulted in the following layout on large screens: chrome -------------------------------------- |…
The translation alert dialog was attached to the entire view in case no
status bar was found. This resulted in the following layout on large
screens:
chrome
--------------------------------------
| alert dialog | form view | chatter |
| | | |
--------------------------------------
Whereas when a status bar was set on the form view, the rendering was as
follow:
chrome
--------------------------------------
| status bar | chatter |
| alert dialog | |
| form view | |
--------------------------------------
The fix make sure the alert dialog is always placed just above the form
view just like when there is a status bar.
Task: 2075172
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#44828
Forward-Port-Of: odoo/odoo#41755In a database with many users / events to synchronize, the cron `ir_cron_sync_all_cals` may time out. Consequently, even if a `commit` is performed for each user, some users are never synchronized. In this commit, we first sort the users by last synchronization date, meaning that all users will ultimately be synchronized, even if the cron times out. On top of that, we introduce the context key `last_sync_hours` to prevent the synchronization in case the cron is restarted after timeout.
Original PR description
In a database with many users / events to synchronize, the cron `ir_cron_sync_all_cals` may time out. Consequently, even if a `commit` is performed for each user, some users are never synchronized. In this commit, we first sort the users by last synchronization date, meaning that all users will ultimately be synchronized, even if the cron times out. On top of that, we introduce the context key `last_sync_hours` to prevent the synchronization in case the cron is restarted after timeout. opw-2158372 Co-authored-by: Nicolas Martinelli <nim@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#44981
* = website_studio It is now possible to change the position of the submit button via the left panel. Some form needed an adaptation. related to: https://github.com/odoo/odoo/pull/44907 task-2191409 Forward-Port-Of: odoo/enterprise#8296
Original PR description
* = website_studio It is now possible to change the position of the submit button via the left panel. Some form needed an adaptation. related to: https://github.com/odoo/odoo/pull/44907 task-2191409 Forward-Port-Of: odoo/enterprise#8296
Forward-Port-Of: odoo/enterprise#8204
Original PR description
Forward-Port-Of: odoo/enterprise#8204
When ISR reference number starts with zeros, those are not mandatory to write. From a user standpoint writing a number of zeros is a pain. Forward-Port-Of: odoo/enterprise#8193
Original PR description
When ISR reference number starts with zeros, those are not mandatory to write. From a user standpoint writing a number of zeros is a pain. Forward-Port-Of: odoo/enterprise#8193
Steps to reproduce the bug: - Install app Consolidation - Uninstall it - Go to Accounting Journal Item menu Bug: A traceback was raised because the search view account.consolidation.move.line.search was not removed. PS: The external id view_account_move_line_filter was duplicated and then the external id of account.consolidation.move.line.search was lost. opw:2186353 Forward-Port-Of: odoo/enterprise#8310
Original PR description
Steps to reproduce the bug: - Install app Consolidation - Uninstall it - Go to Accounting Journal Item menu Bug: A traceback was raised because the search view account.consolidation.move.line.search was not removed. PS: The external id view_account_move_line_filter was duplicated and then the external id of account.consolidation.move.line.search was lost. opw:2186353 Forward-Port-Of: odoo/enterprise#8310
In case of a recurring event, `start_datetime` and `stop_datetime` are `str`, not `datetime`. We make sure to compare `datetime`. opw-2194602 Forward-Port-Of: odoo/enterprise#8326
Original PR description
In case of a recurring event, `start_datetime` and `stop_datetime` are `str`, not `datetime`. We make sure to compare `datetime`. opw-2194602 Forward-Port-Of: odoo/enterprise#8326
Using `line.mapped('sale_line_ids.move_ids')` assumes that the module `sale_stock` is installed. Even if it is auto-installed, it is still possible to uninstall it. [1] https://github.com/odoo/enterprise/blob/39b698f5deddacdc7c06422a88c515e9123bcf39/l10n_mx_edi_landing/models/account_move.py#L14 opw-2193346 Forward-Port-Of: odoo/enterprise#8324
Original PR description
Using `line.mapped('sale_line_ids.move_ids')` assumes that the module
`sale_stock` is installed. Even if it is auto-installed, it is still
possible to uninstall it.
[1] https://github.com/odoo/enterprise/blob/39b698f5deddacdc7c06422a88c515e9123bcf39/l10n_mx_edi_landing/models/account_move.py#L14
opw-2193346
Forward-Port-Of: odoo/enterprise#8324Having this date in the past caused some banks to refuse the SCT file. Forward-Port-Of: odoo/enterprise#8287 Forward-Port-Of: odoo/enterprise#8280
Original PR description
Having this date in the past caused some banks to refuse the SCT file. Forward-Port-Of: odoo/enterprise#8287 Forward-Port-Of: odoo/enterprise#8280
When the sale_subscrition test is run between 00:00:00 and 00:59:00, it crashes with one day difference. With this commit, the test use the context_today method that returns the client side date for today. Forward-Port-Of: odoo/enterprise#8325
Original PR description
When the sale_subscrition test is run between 00:00:00 and 00:59:00, it crashes with one day difference. With this commit, the test use the context_today method that returns the client side date for today. Forward-Port-Of: odoo/enterprise#8325
Also, this patch allows not needing to upgrade the module after this fix https://github.com/odoo/odoo/commit/620b9012333fda3df427d76c5b7e3b72c3920424 in order to make DIOT report work in multi company, as we will only fetch tax repartition lines belonging to a tax we have access to. Forward-Port-Of: odoo/enterprise#8231 Forward-Port-Of: odoo/enterprise#8207
Original PR description
Also, this patch allows not needing to upgrade the module after this fix https://github.com/odoo/odoo/commit/620b9012333fda3df427d76c5b7e3b72c3920424 in order to make DIOT report work in multi company, as we will only fetch tax repartition lines belonging to a tax we have access to. Forward-Port-Of: odoo/enterprise#8231 Forward-Port-Of: odoo/enterprise#8207