Odoo Changelog — 2026-01-03

Saturday, January 3, 2026

6 changes · 19.0

Improvements(1)

Enhancements to existing features

[IMP] account_accountant: Add Link to Deferrals Docs in Settings

Enterprise19.0account_accountant

This update adds a helpful link within the Accounting Settings to Odoo's documentation on Deferred Expenses and Revenue management. This provides users with immediate access to detailed information and best practices for handling these complex accounting processes, improving accuracy and understanding.

Original PR description

In the Accounting Settings, add a "?" icon that points at the Odoo documentation on Deferred Expenses and Revenue management.

task-5418388

Forward-Port-Of: odoo/enterprise#103090

#accounting#documentation#deferred expenses

Bug Fixes(5)

Resolved issues and error corrections

[FIX] website_forum: fix forum post form validation

PR #241935

Core19.0website_forum

This update corrects a bug in the forum post form where fields were incorrectly marked as invalid, even after submitting the post. The change ensures that title and description fields are properly validated, improving the user experience and preventing incorrect form behavior. This fix was implemented as part of a larger refactoring of website widgets.

Original PR description

Steps to reproduce
===================
1. Go to Forum.
2. Select any forum and Click on New Post.
3. Add a title and keep description empty.
4. Post Your Question.
=> The title is marked as invalid.
6. Now add a description.
7. Post Your Question.
=> Both the title and description are marked as invalid, yet form is submitted successfully.

After commit [1], refactoring public widgets to Interactions, the `is-invalid` class toggle for forum post title and description used an incorrect condition, leading to improper highlighting of these fields.

[1] https://github.com/odoo/odoo/commit/22e777c046521f3f89b62caa5876680beb7f5aba

Task-5400394

Forward-Port-Of: odoo/odoo#241540

#website#forum#validation

[FIX] mail: jump to present not working in non-aside chatter

PR #241885

Core19.0mail

This update fixes an issue where the 'Jump to Present' button in non-aside chatter was unreliable, causing flickering and incorrect scrolling. By disabling a browser feature that interfered with scrolling, this change ensures the button reliably jumps to the latest message, improving user experience.

Original PR description

**Description of the issue this PR addresses:**
------------------------------------------------
In non-aside chatter, the **Jump to Present** action did not work reliably. When users clicked it, the view flickered and the scroll position jumped back, preventing users from reaching the latest message.

This happened because the browser’s native scroll anchoring interfered with the scroll-to-bottom behavior when messages were reloaded.

**Current behavior before PR:**
---------------------------------
- In non-aside chatter, clicking **Jump to Present** caused flickering.
- The view jumped back instead of staying on the latest message.
- Users could not reliably reach the most recent messages.

**Desired behavior after PR is merged:**
-----------------------------------------
- Clicking **Jump to Present** in non-aside chatter scrolls directly to the
  latest message without flickering.
- The scroll position remains stable and does not jump back.
- The **Jump to Present** button works consistently.

**Task:** 5264332

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

Forward-Port-Of: odoo/odoo#240934

#chat#communication#user experience

[FIX] l10n_co_edi: add missing qr and payment details

PR #103199

Enterprise19.0l10n_co_edi

This update corrects a technical issue where invoice reports in the l10n_co_edi module were missing crucial QR codes and payment information. The team has extended the existing view to ensure all invoices accurately reflect these details, improving reporting accuracy and compliance. This resolves issues OPW-5385872 and OPW-5414922.

Original PR description

During the commit 6479d17, a new view was added but unfortunately, the details of the previous one was not considered.

To fix this issue, we should extend the values of the main one.

OPW-5385872
OPW-5414922

Forward-Port-Of: odoo/enterprise#103039

#reporting#invoice#compliance

[FIX] point_of_sale: fix crash when switching tab while printing receipt

PR #241936

Core19.0point_of_saleMEDIUM

This update fixes a crash that occurred when switching tabs while a receipt was being printed in Point of Sale. The change ensures the receipt component is correctly loaded and accessible, preventing the printing process from failing. This improves the reliability of automatic receipt printing.

Original PR description

Why it happens:
---------------
The receipt is printed when the parent of the `OrderReceipt`, i.e. `RenderContainer` is rendered. In this case, we assume that `OrderReceipt` has already had the time to be mounted and thus it's in the DOM, so in this case, `this.ref?.el?.firstElementChild` has the order receipt. However, when switching the tab, and since OWL uses `requestAnimationFrame` as a scheduler, and since the browser will throttle `requestAnimationFrame` when the tab is not active, we will not have access to the order receipt component in its parent's `onRendered`!

The fix
-------
Instead of seeing the parent renders as a sign that its child has been successfully put in the DOM, we now renders the child component (OrderReceipt) in its own container and thus we can hook into its `onMounted` lifecycle where we know for sure that this component has been successfully mounted and attached to the DOM, and can be accessed through `this.ref?.el?.firstElementChild`.

opw-5124585

Forward-Port-Of: odoo/odoo#241781
Forward-Port-Of: odoo/odoo#239008

#pos#printing#reliability

[FIX] point_of_sale: prevent leftpane from shrinking below its width

PR #241953

Core19.0point_of_sale

This update fixes a visual issue in the Point of Sale interface where the left-hand product selection pane would sometimes shrink, making text unreadable. The fix ensures the pane maintains its intended width, improving the user experience. The issue was intermittent and related to how the layout elements were interacting.

Original PR description

In some scenarios, although not fully deterministic, the left pane is being pushed by its right pane sibling (i.e. the products grid), making it go below its specified with of `left-pane-width`, and making text non readable.

By setting `flex-shrink: 0` on this element, we tell the browser to respect the specified width, and not allow its siblings to shrink it.

We could have also set `min-width: $left-pane-width;`, but it's less descriptive. The problem happens because we are in a flex container, hencer we use `flex-shrink: 0`.

### Notes:
This issue only happened from time to time for the client, and it seems non deterministic. 
If we disable showing the product images, the issue stops happening.

The below before vs after screenshots are taken on MacBook Pro 14 inches.

### Before:
<img width="1493" height="868" alt="image" src="https://github.com/user-attachments/assets/70bc5a70-34a6-48c9-a60a-ab1de1fa0b9b" />

<img width="1496" height="867" alt="image" src="https://github.com/user-attachments/assets/e8ae9b25-3525-439b-93dd-18dc825613c7" />


### After:
<img width="1495" height="866" alt="Capture d’écran 2025-12-31 à 11 28 38" src="https://github.com/user-attachments/assets/23585d3d-b0bf-4316-8749-b39a56fc8cda" />

<img width="1497" height="866" alt="image" src="https://github.com/user-attachments/assets/f5654163-1dd3-4ff9-bb12-d8cd8fbc497b" />


opw-5392359

Forward-Port-Of: odoo/odoo#241941
Forward-Port-Of: odoo/odoo#241731

#UI#POS#Layout

Steps to reproduce =================== 1. Go to Forum. 2. Select any forum and Click on New Post. 3. Add a title and keep description empty. 4. Post Your Question. => The title is marked as invalid. 6. Now add a description. 7. Post Your Question. => Both the title and description are marked as invalid, yet form is submitted successfully. After commit [1], refactoring public widgets to Interactions, the `is-invalid` class toggle for forum post title and description used an incorrect condition, leading to improper highlighting of these fields. [1] https://github.com/odoo/odoo/commit/22e777c046521f3f89b62caa5876680beb7f5aba Task-5400394 Forward-Port-Of: odoo/odoo#241540

**Description of the issue this PR addresses:** ------------------------------------------------ In non-aside chatter, the **Jump to Present** action did not work reliably. When users clicked it, the view flickered and the scroll position jumped back, preventing users from reaching the latest message. This happened because the browser’s native scroll anchoring interfered with the scroll-to-bottom behavior when messages were reloaded. **Current behavior before PR:** --------------------------------- - In non-aside chatter, clicking **Jump to Present** caused flickering. - The view jumped back instead of staying on the latest message. - Users could not reliably reach the most recent messages. **Desired behavior after PR is merged:** ----------------------------------------- - Clicking **Jump to Present** in non-aside chatter scrolls directly to the latest message without flickering. - The scroll position remains stable and does not jump back. - The **Jump to Present** button works consistently. **Task:** 5264332 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#240934

During the commit 6479d17, a new view was added but unfortunately, the details of the previous one was not considered. To fix this issue, we should extend the values of the main one. OPW-5385872 OPW-5414922 Forward-Port-Of: odoo/enterprise#103039

Steps to reproduce: ------------------- 1. Enable "Automatic Receipt Printing" so the receipt is auto printed after paying an order 2. From PoS, make an order, select it to invoice, and click the pay button. 3. While loading (normally a few seconds to finish the invoice), switch the tab and stay there for few seconds (the time the invoicing has finsihed). 4. Come back to the initial page, a traceback will appear and the ticket is not printed. Why it happens: --------------- The receipt is printed when the parent of the `OrderReceipt`, i.e. `RenderContainer` is rendered. In this case, we assume that `OrderReceipt` has already had the time to be mounted and thus it's in the DOM, so in this case, `this.ref?.el?.firstElementChild` has the order receipt. However, when switching the tab, and since OWL uses `requestAnimationFrame` as a scheduler, and since the browser will throttle `requestAnimationFrame` when the tab is not active, we will not have access to the order receipt component in its parent's `onRendered`! The fix ------- Instead of seeing the parent renders as a sign that its child has been successfully put in the DOM, we now renders the child component (OrderReceipt) in its own container and thus we can hook into its `onMounted` lifecycle where we know for sure that this component has been successfully mounted and attached to the DOM, and can be accessed through `this.ref?.el?.firstElementChild`. opw-5124585 Forward-Port-Of: odoo/odoo#241781 Forward-Port-Of: odoo/odoo#239008

In some scenarios, although not fully deterministic, the left pane is being pushed by its right pane sibling (i.e. the products grid), making it go below its specified with of `left-pane-width`, and making text non readable. By setting `flex-shrink: 0` on this element, we tell the browser to respect the specified width, and not allow its siblings to shrink it. We could have also set `min-width: $left-pane-width;`, but it's less descriptive. The problem happens because we are in a flex container, hencer we use `flex-shrink: 0`. ### Notes: This issue only happened from time to time for the client, and it seems non deterministic. If we disable showing the product images, the issue stops happening. The below before vs after screenshots are taken on MacBook Pro 14 inches. ### Before: <img width="1493" height="868" alt="image" src="https://github.com/user-attachments/assets/70bc5a70-34a6-48c9-a60a-ab1de1fa0b9b" /> <img width="1496" height="867" alt="image" src="https://github.com/user-attachments/assets/e8ae9b25-3525-439b-93dd-18dc825613c7" /> ### After: <img width="1495" height="866" alt="Capture d’écran 2025-12-31 à 11 28 38" src="https://github.com/user-attachments/assets/23585d3d-b0bf-4316-8749-b39a56fc8cda" /> <img width="1497" height="866" alt="image" src="https://github.com/user-attachments/assets/f5654163-1dd3-4ff9-bb12-d8cd8fbc497b" /> opw-5392359 Forward-Port-Of: odoo/odoo#241941 Forward-Port-Of: odoo/odoo#241731