Odoo Changelog — 2026-04-13

Monday, April 13, 2026

10 changes · saas-18.2

Bug Fixes(10)

Resolved issues and error corrections

[FIX] html_editor: flaky inline code formatting test

Coresaas-18.2html_editor

This change makes an automated test for the HTML editor wait until the color picker is ready before choosing a color. It reduces random test failures in build checks, helping keep releases and validations more dependable without changing user-facing behavior.

Original PR description

Purpose of this PR:

- Ensure color picker is rendered before selecting a color to avoid non-deterministic failures.

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#258566

#test stability#html editor#color picker

[FIX] sale: ensure negative discounts are not displayed in reports

PR #258614

Coresaas-18.2sale

Sales PDFs now match the online customer preview by hiding negative discount values on order lines. This removes an inconsistency that could confuse customers or sales teams when comparing the preview with the generated document.

Original PR description

Steps to produce:
---
- Install the `Sales` module.
- Enable discounts from settings.
- Create a Sale Order with a negative discount on an order line.
- Preview the Sale Order and click on the view details button.

Issue:
---
- Negative discount values are not shown in the preview (portal view), but they are displayed in the generated PDF.

Root cause:
---
- At [1], the portal template includes a condition to display discounts only when they are greater than 0, while the report templates lack this check, leading to inconsistent behavior.

Solution:
---
- Applied the same condition in the report templates to align the PDF output with the portal preview behavior.

Before:
---
<img width="787" height="136" alt="image" src="https://github.com/user-attachments/assets/d32311be-4aec-4d6f-b905-d5e52f712ba4" />

After:
---
<img width="775" height="139" alt="image" src="https://github.com/user-attachments/assets/2614a8ad-dca6-49ca-b720-5c234aa91cf6" />


[1]https://github.com/odoo/odoo/blob/0f463fd247d2f5da79d6ec2b6bec18774f6f600b/addons/sale/views/sale_portal_templates.xml#L539

Enterprise PR: https://github.com/odoo/enterprise/pull/111916

opw-6061568

Forward-Port-Of: odoo/odoo#258480
Forward-Port-Of: odoo/odoo#255735

[FIX] sale: translate 'View Quotation' for followers

PR #257349

Coresaas-18.2sale

Quotation and sales order notification emails now translate the action button fully into each recipient's language. This avoids mixed-language wording for followers and provides a clearer, more consistent customer communication experience.

Original PR description

When sending a quotation or sales order via email to a follower, the action button in the notification (e.g., "View Quotation") was appearing partially translated in the recipient's language.

The issue came from the document description being explicitly evaluated using the sender's language context usually English) during the email composition phase, so it could not be correctly re-translated by the mail engine when rendering the final layout for a recipient using a different language.

This commit allows the language context to be dynamic when preparing the document description for the email composer, ensuring the action button is fully and accurately translated.

---
opw-5976084

Forward-Port-Of: odoo/odoo#256077

#translation#email#quotation#sales order

[FIX] mail: keep Jump to Present button visible in chatter

PR #258475

Coresaas-18.2mail

The chatter now more reliably shows the Jump to Present button when users scroll away from the latest messages. This helps users quickly return to current conversation activity, regardless of message length or layout.

Original PR description

**Description of the issue this PR addresses:**
----------------------------------------------
In 18.0, the Jump to Present button in chatter could fail to
appear when the user scrolled away from the latest messages.

**Current behavior before PR:**
----------------------------------------------
- The present detection threshold relied on both viewport height and the cumulative height of recent messages.
- In some chatter layouts, this threshold could exceed the visible area, preventing the Jump to Present button from appearing.

**Desired behavior after PR is merged:**
----------------------------------------------
- The present threshold is based only on the viewport height.
- The Jump to Present button appears consistently regardless of message size or chatter layout.

Task-5435586

----------------------------------------------
I confirm I have signed the CLA and read the PR guidelines at https://www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#246299

#chatter#navigation#usability

[FIX] account: fix RTL brackets in invoice PDF

PR #258477

Coresaas-18.2account

Invoice PDFs printed in English now display Arabic product names with parentheses in the correct order. This prevents confusing or unprofessional-looking invoice descriptions for customers using mixed English and Arabic content.

Original PR description

**Steps to reproduce:**
1. Create a product named: لوحة توزيع كهربائية 100 أمبير (شنايدر )
2. Create an invoice with that product
3. Print the invoice PDF in English
4. Observe the brackets are misplaced in the description column

**Current behavior:**
Parentheses appear detached from the Arabic word they enclose, floating at the wrong end of the text.

**Expected behavior:**
Parentheses correctly wrap the enclosed Arabic text.

**Cause of the issue:**
Odoo's report CSS sets `direction: ltr` on elements that are ancestors of the line description span. When CSS `direction: ltr` targets the same element as `dir="auto"`, wkhtmltopdf's WebKit engine lets the CSS rule win, keeping the paragraph base direction as LTR. The Unicode BiDi algorithm then resolves parentheses (neutral characters) using LTR as the base direction, misplacing them.

**Fix:**
Placing `dir="auto"` directly on the `<span>` that renders the line description — rather than the parent `<td>` — avoids the CSS override. wkhtmltopdf then detects the first strong character (Arabic) and uses RTL as the base direction for that span, allowing the BiDi algorithm to correctly position the brackets.

opw-5884712

Forward-Port-Of: odoo/odoo#257881
Forward-Port-Of: odoo/odoo#251190

[FIX] hr_payroll: fix payslip warning bug

PR #112684

Enterprisesaas-18.2hr_payroll

This update corrects a misleading warning message displayed when an employee's contract overlaps with a payslip period. The change ensures that a warning only appears when a contract genuinely runs over the payslip date, improving user experience and preventing unnecessary alerts. This resolves an issue identified in older versions of Odoo Enterprise.

Original PR description

[FIX] hr_payroll: fix payslip warning bug Bug reproduction: 1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well) 2 - Create an employee and make…

[FIX] hr_payroll: fix payslip warning bug

Bug reproduction:
    1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well)
    2 - Create an employee and make its contract from 01-01-2025 to 05-03-2026 (DD/MM/YYYY) format.
    3 - Generate payslip for March, the warning of "The period selected does not match the contract validity period" popups.
    4 - But we do not want that, even though there is 1 overlapping day in contract with payslip we can continue.

Bug cause:
    1 - In >= v.17 (not in v.19), there was a warning, when the contract dates do not fully contains the payslip dates, the warning was appearing.
    2 - In v.19 it is not the case, when there is a contract that overlaps at least one dat of the payslip then we are fine, if no overlap then no contract on payslip warning should appear

Bug solution:
    1 - I replaced old warning "The period selected does not match the contract validity period" with the one in v.19 "No running contract over payslip period"

Tests:
    1 - There was a unit test about old warning (test_payslip_warnings), I changed that parts.
    2 - I added further steps to the existing test about the new warning that should appear (No running contract over payslip period)

Note: Implemented feature: need to check what happens after v.17, should be removed in v.19 latest, maybe before as well.

task - 6006693

Forward-Port-Of: odoo/enterprise#109791

[FIX] web_studio: fix crash when dblclick in list view

PR #113299

Enterprisesaas-18.2web_studio

This update resolves a crash that occurred when users double-clicked 'Add Custom Field' within a list view's optional fields dropdown in Odoo Studio. The fix ensures Studio is properly protected from opening multiple instances, preventing the instability.

Original PR description

On a list view, open the optional fields dropdown. Click twice on "Add Custom Field"

Before this commit there was a crash, because opening studio while it is already opening was not protected.

After this commit, there is no crash.

#optional fields#list view#studio

[FIX] hr_payroll: fix payslip warning bug

PR #113624

Enterprisesaas-18.2hr_payroll

This update corrects a misleading warning message displayed during payslip generation. The fix ensures that a warning only appears when a contract genuinely overlaps with the payslip period, improving user experience and preventing unnecessary alerts. This change was made to align with the behavior introduced in version 19.

Original PR description

Bug reproduction:
    1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well)
    2 - Create an employee and make its contract from 01-01-2025 to 05-03-2026 (DD/MM/YYYY) format.
    3 - Generate payslip for March, the warning of "The period selected does not match the contract validity period" popups.
    4 - But we do not want that, even though there is 1 overlapping day in contract with payslip we can continue.

Bug cause:
    1 - In >= v.17 (not in v.19), there was a warning, when the contract dates do not fully contains the payslip dates, the warning was appearing.
    2 - In v.19 it is not the case, when there is a contract that overlaps at least one dat of the payslip then we are fine, if no overlap then no contract on payslip warning should appear

Bug solution:
    1 - I replaced old warning "The period selected does not match the contract validity period" with the one in v.19 "No running contract over payslip period"

Tests:
    1 - There was a unit test about old warning (test_payslip_warnings), I changed that parts.
    2 - I added further steps to the existing test about the new warning that should appear (No running contract over payslip period)

Last Test Update:
    1 - I noticed that contract date changes was not affecting the warning appearance directly
    2 - Unit test is expanded with contract date change and observing the warning appearance

Note: Implemented feature: need to check what happens after v.17, should be removed in v.19 latest, maybe before as well.

task - 6006693

Forward-Port-Of: odoo/enterprise#113566
Forward-Port-Of: odoo/enterprise#112758

[FIX] l10n_be_hr_payroll: Update FFE rates to 2026

PR #113636

Enterprisesaas-18.2l10n_be_hr_payroll

This update adjusts Belgian payroll tax rates (FFE) to reflect the latest regulations for 2026. This ensures accurate tax calculations and compliance with Belgian tax laws within the Odoo Enterprise system. The change is a technical fix to maintain accurate financial reporting.

Original PR description

Forward-Port-Of: odoo/enterprise#113426

#payroll#belgium#taxes#hr

[FIX] website_appointment_sale: translate booking description to website language

PR #113197

Enterprisesaas-18.2website_appointment_sale

This update fixes an issue where appointment booking descriptions were displayed in the user's language instead of the website's language. Previously, the system used the user's language setting. Now, booking descriptions will correctly display in the website's specified language (e.g., French), ensuring a consistent user experience across different language settings.

Original PR description

When booking an appointment, the cart shows the date/time in the partner's language instead of the website's language. `_prepare_order_line_values` uses `self.partner_id.lang`, ignoring the website language and using the user's language instead.

Steps to reproduce:
1. Have a website language different than the user's language
2. Go to the website appointment page
3. Book an appointment
4. Check the booking

For this case:
- Website language: French
- User language: English

=> You will find,  "xxx at xx:xx to yyy at yy:yy" instead of  "xxx à xx:xx au yyy à yy:yy"

Ticket [link](https://www.odoo.com/odoo/action-4043/5931610)
opw-5931610

Forward-Port-Of: odoo/enterprise#107698

#localization#booking#website

Purpose of this PR: - Ensure color picker is rendered before selecting a color to avoid non-deterministic failures. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#258566

Steps to produce: --- - Install the `Sales` module. - Enable discounts from settings. - Create a Sale Order with a negative discount on an order line. - Preview the Sale Order and click on the view details button. Issue: --- - Negative discount values are not shown in the preview (portal view), but they are displayed in the generated PDF. Root cause: --- - At [1], the portal template includes a condition to display discounts only when they are greater than 0, while the report templates lack this check, leading to inconsistent behavior. Solution: --- - Applied the same condition in the report templates to align the PDF output with the portal preview behavior. Before: --- <img width="787" height="136" alt="image" src="https://github.com/user-attachments/assets/d32311be-4aec-4d6f-b905-d5e52f712ba4" /> After: --- <img width="775" height="139" alt="image" src="https://github.com/user-attachments/assets/2614a8ad-dca6-49ca-b720-5c234aa91cf6" /> [1]https://github.com/odoo/odoo/blob/0f463fd247d2f5da79d6ec2b6bec18774f6f600b/addons/sale/views/sale_portal_templates.xml#L539 Enterprise PR: https://github.com/odoo/enterprise/pull/111916 opw-6061568 Forward-Port-Of: odoo/odoo#258480 Forward-Port-Of: odoo/odoo#255735

When sending a quotation or sales order via email to a follower, the action button in the notification (e.g., "View Quotation") was appearing partially translated in the recipient's language. The issue came from the document description being explicitly evaluated using the sender's language context usually English) during the email composition phase, so it could not be correctly re-translated by the mail engine when rendering the final layout for a recipient using a different language. This commit allows the language context to be dynamic when preparing the document description for the email composer, ensuring the action button is fully and accurately translated. --- opw-5976084 Forward-Port-Of: odoo/odoo#256077

**Description of the issue this PR addresses:** ---------------------------------------------- In 18.0, the Jump to Present button in chatter could fail to appear when the user scrolled away from the latest messages. **Current behavior before PR:** ---------------------------------------------- - The present detection threshold relied on both viewport height and the cumulative height of recent messages. - In some chatter layouts, this threshold could exceed the visible area, preventing the Jump to Present button from appearing. **Desired behavior after PR is merged:** ---------------------------------------------- - The present threshold is based only on the viewport height. - The Jump to Present button appears consistently regardless of message size or chatter layout. Task-5435586 ---------------------------------------------- I confirm I have signed the CLA and read the PR guidelines at https://www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#246299

**Problem:** When printing an invoice in English (LTR report) with a product whose name contains Arabic text and parentheses (e.g., لوحة توزيع كهربائية 100 أمبير (شنايدر )), the brackets appear in the wrong position in the generated PDF. **Steps to reproduce:** 1. Create a product named: لوحة توزيع كهربائية 100 أمبير (شنايدر ) 2. Create an invoice with that product 3. Print the invoice PDF in English 4. Observe the brackets are misplaced in the description column **Current behavior:** Parentheses appear detached from the Arabic word they enclose, floating at the wrong end of the text. **Expected behavior:** Parentheses correctly wrap the enclosed Arabic text. **Cause of the issue:** Odoo's report CSS sets `direction: ltr` on elements that are ancestors of the line description span. When CSS `direction: ltr` targets the same element as `dir="auto"`, wkhtmltopdf's WebKit engine lets the CSS rule win, keeping the paragraph base direction as LTR. The Unicode BiDi algorithm then resolves parentheses (neutral characters) using LTR as the base direction, misplacing them. **Fix:** Placing `dir="auto"` directly on the `<span>` that renders the line description — rather than the parent `<td>` — avoids the CSS override. wkhtmltopdf then detects the first strong character (Arabic) and uses RTL as the base direction for that span, allowing the BiDi algorithm to correctly position the brackets. opw-5884712 Forward-Port-Of: odoo/odoo#257881 Forward-Port-Of: odoo/odoo#251190

[FIX] hr_payroll: fix payslip warning bug Bug reproduction: 1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well) 2 - Create an employee and make its contract from 01-01-2025 to 05-03-2026 (DD/MM/YYYY) format. 3 - Generate payslip for March, the warning of "The period selected does not match the contract validity period" popups. 4 - But we do not want that, even though there is 1 overlapping day in contract with payslip we can continue. Bug cause: 1 - In >= v.17 (not in v.19), there was a warning, when the contract dates do not fully contains the payslip dates, the warning was appearing. 2 - In v.19 it is not the case, when there is a contract that overlaps at least one dat of the payslip then we are fine, if no overlap then no contract on payslip warning should appear Bug solution: 1 - I replaced old warning "The period selected does not match the contract validity period" with the one in v.19 "No running contract over payslip period" Tests: 1 - There was a unit test about old warning (test_payslip_warnings), I changed that parts. 2 - I added further steps to the existing test about the new warning that should appear (No running contract over payslip period) Note: Implemented feature: need to check what happens after v.17, should be removed in v.19 latest, maybe before as well. task - 6006693 Forward-Port-Of: odoo/enterprise#109791

On a list view, open the optional fields dropdown. Click twice on "Add Custom Field" Before this commit there was a crash, because opening studio while it is already opening was not protected. After this commit, there is no crash.

Bug reproduction: 1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well) 2 - Create an employee and make its contract from 01-01-2025 to 05-03-2026 (DD/MM/YYYY) format. 3 - Generate payslip for March, the warning of "The period selected does not match the contract validity period" popups. 4 - But we do not want that, even though there is 1 overlapping day in contract with payslip we can continue. Bug cause: 1 - In >= v.17 (not in v.19), there was a warning, when the contract dates do not fully contains the payslip dates, the warning was appearing. 2 - In v.19 it is not the case, when there is a contract that overlaps at least one dat of the payslip then we are fine, if no overlap then no contract on payslip warning should appear Bug solution: 1 - I replaced old warning "The period selected does not match the contract validity period" with the one in v.19 "No running contract over payslip period" Tests: 1 - There was a unit test about old warning (test_payslip_warnings), I changed that parts. 2 - I added further steps to the existing test about the new warning that should appear (No running contract over payslip period) Last Test Update: 1 - I noticed that contract date changes was not affecting the warning appearance directly 2 - Unit test is expanded with contract date change and observing the warning appearance Note: Implemented feature: need to check what happens after v.17, should be removed in v.19 latest, maybe before as well. task - 6006693 Forward-Port-Of: odoo/enterprise#113566 Forward-Port-Of: odoo/enterprise#112758

When booking an appointment, the cart shows the date/time in the partner's language instead of the website's language. `_prepare_order_line_values` uses `self.partner_id.lang`, ignoring the website language and using the user's language instead. Steps to reproduce: 1. Have a website language different than the user's language 2. Go to the website appointment page 3. Book an appointment 4. Check the booking For this case: - Website language: French - User language: English => You will find, "xxx at xx:xx to yyy at yy:yy" instead of "xxx à xx:xx au yyy à yy:yy" Ticket [link](https://www.odoo.com/odoo/action-4043/5931610) opw-5931610 Forward-Port-Of: odoo/enterprise#107698