Odoo Changelog — 2025-02-20

Thursday, February 20, 2025

59 changes · saas-18.2

Improvements(2)

Enhancements to existing features

[IMP] mail, various: cleanup default recipients (overrides)

PR #198173

Coresaas-18.2calendarcrmeventmailmass_mailingtest_mailtest_mass_mailingwebsite_event_track

This update simplifies how Odoo chooses default email recipients across several apps by relying more on shared base logic instead of custom per-app rules. It should make recipient selection easier to maintain and more consistent, with fixes for cases involving normalized email addresses and primary contact emails.

Original PR description

RATIONALE Cleanup addon-specific code about default recipients computation. Since base code is now smarter, most overrides can be removed to keep simple code and ease understanding. SPECIFICATIONS…

RATIONALE

Cleanup addon-specific code about default recipients computation. Since
base code is now smarter, most overrides can be removed to keep simple
code and ease understanding.

SPECIFICATIONS

Remove overrides that are now covered by base computation.

When necessary use '_mail_defaults_to_email' that prioritizes email
over partner (customer) when searching for default recipients.

When necessary add missing '_primary_email' definition allowing to find
the main email to contact.

Provide some fixes in default recipients computation, notably linked to
normalized emails usage and comparison instead of raw emails.

QUERIES

Simple overrides on test models are removed. This implies usage of
more complete '_message_get_default_recipients' hence some additional
queries.

LINKS

Followup of odoo/odoo#172714: improve default behavior of templates
Followup of odoo/odoo#188642 : main branch for email-like recipients

Task-4555506: Cleanup / Mergeup default / suggested recipients

#email#recipients#maintenance#consistency

[IMP] mail, various: cleanup default recipients (overrides)

PR #79590

Enterprisesaas-18.2helpdeskhr_contract_salarymail

This update simplifies how default email recipients are selected across several Odoo apps by relying more on shared platform logic instead of custom overrides. It improves consistency for email templates and recipient suggestions, with specific fixes for salary offer communications and normalized email matching.

Original PR description

RATIONALE Cleanup addon-specific code about default recipients computation. Since base code is now smarter, most overrides can be removed to keep simple code and ease understanding. SPECIFICATIONS…

RATIONALE

Cleanup addon-specific code about default recipients computation. Since
base code is now smarter, most overrides can be removed to keep simple
code and ease understanding.

SPECIFICATIONS

Remove overrides that are now covered by base computation.

When necessary use '_mail_defaults_to_email' that prioritizes email
over partner (customer) when searching for default recipients.

When necessary add missing '_primary_email' definition allowing to find
the main email to contact.

Provide some fixes in default recipients computation, notably linked to
normalized emails usage and comparison instead of raw emails.

QUERIES

Simple overrides on test models are removed. This implies usage of
more complete '_message_get_default_recipients' hence some additional
queries.

LINKS

Followup of odoo/odoo#172714: improve default behavior of templates
Followup of odoo/odoo#188642 : main branch for email-like recipients

Task-4555506: Cleanup / Mergeup default / suggested recipients

Bug Fixes(3)

Resolved issues and error corrections

[MOV] l10n_be_reports(_loans): demo loading in right module

PR #79853

Enterprisesaas-18.2l10n_be_reportsl10n_be_reports_loans

Installing Belgian reports with invoicing will no longer automatically pull in loan features and the full accounting app. A small connector module now loads the loan-related demo content only when both Belgian reports and loans are installed, keeping lighter setups simpler.

Original PR description

Previously, `l10n_be_reports` was depending on `account_loans` because it already depended on `account_reports` which depended on `account_accountant`. `account_loans` also depended on `account_accountant` so this was not a problem.

Now this is not true anymore, we might install `l10n_be_reports` with just invoicing, and not the full accounting. This means that by installing `l10n_be_reports`, we would trigger the installation of `account_loans` which would install the full accounting. So now, instead of relying on the dependency chain, we create a new bridge module between `l10n_be_reports` and `account_loans` which will be autoinstalled if both modules are installed. So if you only install `l10n_be_reports`, you will not have `account_loans` (and the full accounting) installed too.

task-none

Other(54)

Miscellaneous changes

[FW][IMP] stock: hide XLSX export action in quant list view for moves

PR #197972

Coresaas-18.2stock

The cogwheel dropdown menu is unwanted and only contains the 'Export All' button, which is disabled with an attribute. This commit extends the existing base tree view for this specific use to avoid interfering with other views that use/extend it. Task ID: [4471980](https://www.odoo.com/odoo/project/966/tasks/4471980) Forward-Port-Of: odoo/odoo#195148 Forward-Port-Of: odoo/odoo#193987

Original PR description

The cogwheel dropdown menu is unwanted and only contains the 'Export All' button, which is disabled with an attribute. This commit extends the existing base tree view for this specific use to avoid interfering with other views that use/extend it.

Task ID: [4471980](https://www.odoo.com/odoo/project/966/tasks/4471980)

Forward-Port-Of: odoo/odoo#195148
Forward-Port-Of: odoo/odoo#193987

[FW][FIX] web: filter duplicate selected records from the list view

RATIONALE Cleanup addon-specific code about default recipients computation. Since base code is now smarter, most overrides can be removed to keep simple code and ease understanding. SPECIFICATIONS Remove overrides that are now covered by base computation. When necessary use '_mail_defaults_to_email' that prioritizes email over partner (customer) when searching for default recipients. When necessary add missing '_primary_email' definition allowing to find the main email to contact. Provide some fixes in default recipients computation, notably linked to normalized emails usage and comparison instead of raw emails. QUERIES Simple overrides on test models are removed. This implies usage of more complete '_message_get_default_recipients' hence some additional queries. LINKS Followup of odoo/odoo#172714: improve default behavior of templates Followup of odoo/odoo#188642 : main branch for email-like recipients Task-4555506: Cleanup / Mergeup default / suggested recipients

Previously, `l10n_be_reports` was depending on `account_loans` because it already depended on `account_reports` which depended on `account_accountant`. `account_loans` also depended on `account_accountant` so this was not a problem. Now this is not true anymore, we might install `l10n_be_reports` with just invoicing, and not the full accounting. This means that by installing `l10n_be_reports`, we would trigger the installation of `account_loans` which would install the full accounting. So now, instead of relying on the dependency chain, we create a new bridge module between `l10n_be_reports` and `account_loans` which will be autoinstalled if both modules are installed. So if you only install `l10n_be_reports`, you will not have `account_loans` (and the full accounting) installed too. task-none

Before this PR, the chat bot would continue even after forwarding an operator to the visitor when the step contained a message. Steps to reproduce: - Create a chat bot script with three steps: "text", "free_input_single", "fw_operator" with a message set. - Start the bot as a visitor, the operator is correctly added to the channel but the input is not available, the conversation is considered as ended. This is due to a race conditions when processing the notifications coming on the bus. When the message is posted, the operator is not yet added, this information is sent on the bus. When the operator is added, another payload is sent on the bus informing an operator was found. However, the processing of the message notification is delayed and comes after the processing of the newest information, leading to an incorrect state. To solve this issue, ensure insertions are made immediately in the new message handler and send updated data on the bus to ensure the state is correct. This PR also fixes identifying fields issue wiht chat bot steps (step is identified by script step and message not channel. opw-4514479 Forward-Port-Of: odoo/odoo#197242 Forward-Port-Of: odoo/odoo#196584

Versions: --------- 18.0+ Issue: ------ When uploading a document using the `Upload` button, the document is always assigned to the user's main company, regardless of the selected company. Steps to Reproduce: ------------------- 1. Create a secondary company that the current user can access. 2. Navigate to Sales / Configuration / Sales Orders / Headers/Footers. 3. Switch the user's current company to the secondary company. 4. Click the `Upload` button and select any document. - Notice that no document is added to the secondary company's scope. 5. Switch back to the primary company. - The uploaded document is available under the primary company instead of the secondary one. Cause: ------ During the upload process, no company-specific information is provided to associate the document with the selected company. Due to the inheritance of the `ir.attachment` model, it uses `self.env.company` as the default company value for the document[^1]. Because the upload happens via the `HttpDispatcher`, no `allowed_company_ids` context value is provided to the request. Without this context value present, `request.env.company` defaults to the main company of the current user[^2]. Fix: ---- Use the `company_id` associated with the relevant `sale.order.template` (`False` when uploading documents not linked to a template). opw-4472602 [^1]: https://github.com/odoo/odoo/blob/d99e44f22634ac589a940d85fab84ca2b2e85332/odoo/addons/base/models/ir_attachment.py#L408-L409 [^2]: https://github.com/odoo/odoo/blob/d99e44f22634ac589a940d85fab84ca2b2e85332/odoo/api.py#L680-L681 Forward-Port-Of: odoo/odoo#197999 Forward-Port-Of: odoo/odoo#196842

Description of the issue/feature this PR addresses: This PR aims to add better visibility to own checks. Made voided and debited checks appear gray on tree view in order to make handed checks more eye-catching. I also refactor the labels on search views for own and third party checks to make them consistent with "Issue state" field. Lastly, I refactored account.payment tree view to make decoration-muted work well when "state" is "Canceled". Current behavior before PR: - l10n_latam_check Debited checks records appear black on tree view, and "Issue state" tag on green. Voided checks records appear gray on tree view as well as "Issue state" tag. ![image](https://github.com/user-attachments/assets/2c8aa165-e544-448e-a1b5-7fb257c717c6) - account "Canceled" payments records appear black on tree view. Desired behavior after PR is merged: - l10n_latam_check Voided or debited checks records will appear with gray color on tree view, as well as "Issue state" tag. Handed checks records will appear blue on tree view, as well as "Issue state" tag. ![image](https://github.com/user-attachments/assets/7da1eb9b-9d5d-462b-a744-04072bea0a1b) - account "Canceled" payments records appear gray on tree view. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#197515 Forward-Port-Of: odoo/odoo#195595

Steps to reproduce the bug: - Ceate a product - add a new attribute with "variant creation mode" = "Dynamic" - create a BoM for this product - make sure to add an operation in the operational lines of the bom - Click on the BoM smart button then BoM overview smart button Problem: Traceback is raise, because in the BoM overview it creates a BoM report, and it adds the operational lines(operations) to the report, some operations are skipped based on the function `_match_all_variant_values` that checks if the product has all the variant values. This function expects a product to run on, but in case of dynamic attribute a product will only be created if it is included in a sales order, hence the product is empty and the function raise the exception. Since the BoM report is for the product variants, then we can skip the operational line if no product is used in the BoM, and hence the `_match_all_variant_values` won't be called over empty product. opw-4518723 **Possible approaches for the Issue**: 1- Change the product variable in the bom object in the _get_bom_data function to be the product.template instead of the concrete product, this will affect many other functions in the generating of the bom report as **_get_resupply_route_info** function that calls **_get_rules_from_location** which is not a function on the 'product.template' model. Considering that approach requires anticipating the case of having the product.template in the bom in all the sections in the bom report. 2- Keep the porduct in the bom object empty one since we don't have with dynamic attributes. And we just skip operational lines if the porduct is empty so the **_match_all_variant_values** is not called. [**IMPLEMENTED**] (This change doesn't require more changes as everything will be still working with the expected model type 'product.product' but the operations and other data will be empty in the report which make sense because they are variant related ) Current behavior before PR: the app show error whenever a BoM overview smart button is clicked for a BoM of a product with dynamic attribute variants Desired behavior after PR is merged: The BoM overview report should be shown normally with no problems. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196264

Here is description of modifications for each tour: modified: addons/barcodes/static/src/barcode_handlers.js Use hoot event instead of custom event defined in macro.js to uniform code and behaviors. modified: addons/l10n_br_website_sale/static/tests/tours/brazilian_address.js Add a delay to wait the form is loaded to avoid problem with _selectState(id) function. modified: addons/point_of_sale/static/tests/tours/utils/chrome_util.js Use waitFor in run of step because .fa-circle-o-notch should not appears ... then of course body:not(:has(.fa-circle-o-notch)) also not and then tour crashes. modified: addons/pos_self_order/static/tests/tours/self_order_kiosk_tour.js Because of the background animation, clicking on order now may not do anything... so we'll click until we get to take out. modified: addons/pos_self_order/tests/test_self_order_kiosk.py Let's see comment of previous file ... We could need more time for the tours. modified: addons/test_website/static/tests/tours/restricted_editor.js :contains(text) => Check that textContent.test(regex) :has(class) => Check the element classList contains the class modified: addons/website/static/tests/tours/html_editor.js Additionnal steps to ensure tour take the good way. modified: addons/website_slides/static/tests/tours/slides_tour_tools.js Uniformize the behavior for two tours with clickOnAddTagDropdown 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#198214 Forward-Port-Of: odoo/odoo#197871

**Current behavior:** For `real_time`, `avco` prod: When posting the bill of a reception which originated from a PO with a foreign currency, if a return for the receipt was generated as well as a return for that return, there will be an extraneous SVL created which illogically affects the product's `standard_price` (product value has increased from nowhere). **Expected behavior:** The product cost prior to posting the bill and after posting the bill is equal. **Steps to reproduce:** 1. Create an `avco` + `real_time` costing/valuated productA 2. Activate 2 additional currencies + give them unique exchange rates 3. Create a purchase order in the first of the two additional currencies, for `N` units of productA at $`price_unit` 4. Confirm the PO -> receive the product 5. Create another purchase order in the second of the two currencies, again `N` units @ $`price_unit` 6. Confirm + receive, then generate a return for this reception 7. Generate a return for the return of step 6 8. Note the current `standar_price` of ProductA 9. For the second purchase order (the one with the returns) create the vendor bill 10. Observe that the `standard_price` of ProductA has increased without any legitimate basis **Cause of the issue:** In `_generate_price_difference_vals`: https://github.com/odoo/odoo/blob/55658e7f43375d7e1af07293e2cd9d1cc4b33883/addons/purchase_stock/models/account_move_line.py#L307-L314 We operate with the assumption that, because we are in a return of a return, any existing pdiff will have already been compensated for- so we take the POL price unit at face value to compare with the AML price unit. But, in case the POL and AML are in different currencies, this will fail to prevent a pdiff SVL from being created. **Fix:** Convert the purchase line's returned price unit to the currency used by the layer for which we are finding the pdiff. opw-4334372 Forward-Port-Of: odoo/odoo#198129 Forward-Port-Of: odoo/odoo#196222

Issue: The grid elements on the import Lots dialog are placed in one column instead of two, which misses up the layout. Reproduction steps: 1. install "purchase_stock" 2. create a product tracked by lots 3. make an RFQ for that product and confirm it 4. click on the generated receipt smart button 5. in "Operations" tab, click fa-list icon to open the dialog 6. in the dialog, click "Import Serials/Lots Reason: The bug was introduced in [239e75b1385fa023e97396baa0c8d46c50997dda](https://github.com/odoo/odoo/commit/239e75b1385fa023e97396baa0c8d46c50997dda#diff-1377579fdb76de80cd31ca67d798b752a90600ab4c82a3c8799786a130b7a46fR431-R433), where the following style was added ```css .o_cell:first-child:last-child { grid-column: span 2; } ``` which applies for the children of the first and the third grid elements; However, since the first and the third grid elements have `display: contents`, the `grid-column: span 2` of their children messes up the grid layout, and makes it 4x1 instead of 2x2. The fix: Remove `display: contents` on the first and third grid elements, as it seems to not be useful. Have tested on web and mobile layouts. opw-4505725 Forward-Port-Of: odoo/odoo#198050 Forward-Port-Of: odoo/odoo#195396

Improvements(2)

[IMP] mail, various: cleanup default recipients (overrides)

[IMP] mail, various: cleanup default recipients (overrides)

Bug Fixes(3)

[MOV] l10n_be_reports(_loans): demo loading in right module

Other(54)

[FW][IMP] stock: hide XLSX export action in quant list view for moves

[FW][FIX] web: filter duplicate selected records from the list view

Improvements(2)

[IMP] mail, various: cleanup default recipients (overrides)

[IMP] mail, various: cleanup default recipients (overrides)

Bug Fixes(3)

[MOV] l10n_be_reports(_loans): demo loading in right module

Other(54)

[FW][IMP] stock: hide XLSX export action in quant list view for moves

[FW][FIX] web: filter duplicate selected records from the list view

[FIX] pos_urban_piper: prevent archiving of required products

[FIX] documents: restore manage versions in the action

[FW][FIX] website: make tour work without demo data

[FW][FIX] mail: remove false positive when checking message features [17.4]

[FW][FIX] im_livechat: fix fw operator step with message

[FW][FIX] mail: keep composer when livechat has ended for operator (2)

[FW][FIX] mail: improved UI of collapse/expand call participants button

[FW][FIX] core: typo in config.load

[FW][FIX] web: pivot: fix tests failing randomly

[FW][FIX] sale_pdf_quote_builder: provide company_id to quotation documents

[FW][FIX] survey: make "Votes" translatable

[FW][FIX] pos_restaurant: prevent blank screen when canceling an order

[FW][FIX] rating: Remove extra border line on rating image

[FW][FIX] web_editor: prevent unnecessary `feff` wrapping in links

[FW][FIX] point_of_sale: fix line with note from still being marked as changed after ordering

[FW][FIX] purchase: no purchase tab if purchase not installed

[FW][FIX] event_crm: allow syncing of multi-event leads

[FW][FIX] web, website_sale: support WEBP transparency

[FW][FIX] mail: not overlapping with document button

[FW][FIX] web_editor: editing link should not convert to telephone url

[FW][FIX] web_editor: color not getting applied on single selected cell

[FW][IMP] l10n_latam_check, account: tree and search view ux improvements

[FW][FIX] mrp: acces bom overview for dynamic product variant

[FW][IMP] l10n_sk: new VAT rates for 2025

[FW][FIX] stock: display correct description 3 step incoming

[FW][FIX] *: multiple tours

[FW][REF] web: manage errors in macro

[FW][I18N] l10n_eu_oss: add translations

[FW][FIX] website_sale_collect: add tour to test the flow

[FW][18.0][FIX] l10n_fr_account: fix call preserve_existing_tags_on_taxes()

[FW][FIX] point_of_sale: not make product search accent sensitive

[FW][FIX] web: menu_id fallback

[FW][IMP] hw_posbox_homepage: add pairing instructions

[FW][FIX] spreadsheet: display frozen message when needed

[FW][FIX] point_of_sale: fix customer display auto scroll

[FW][FIX] purchase_stock: no extra SVL on return of return with exch. diff

[FW][FIX] html_editor: properly check formatted nodes

[FW][FIX] stock: fix import lots dialog layout

[FW][FIX] hr: fix traceback when clicking plans smart button in hr department

[FW][FIX] sale_commission: several feedbacks

[FW][FIX] web_cohort: fix test failing randomly

[FW][DRAFT][FIX] stock_barcode: fix domain for product form in Inventory Count

[FW][FIX] delivery_sendcloud: Check default value of shipping functionalities

[FW][IMP] hr_attendance_gantt: make gantt_progress_bar domain inheritable

[FW][FIX] document_hr_payroll: set employee as contact of his declarations

[FW][FIX] industry_fsm_sale_report: prevent error on installing module

[FW][FIX] stock_barcode: display description picking

[FW][FIX] {test_}marketing_automation: flush before SELECT

[FW][I18N] l10n_eu_oss_reports: add translations

[FW][FIX] l10n_fr_fec_import: Fix currency rounding

[FW][FIX] documents_spreadsheet: display frozen message when needed

[FW][FIX] account_loans: state assignment when skip_until_date

[FW][FIX] l10n_in_reports_gstr_pos: fallback to POS journal default account for HSN computations

[FW][FIX] l10n_es_reports: January 2025 update 303