Odoo Changelog — 2026-01-28

Wednesday, January 28, 2026

6 changes

Branch: master

5 changes

Refactoring(5)

Code cleanup and technical improvements

[REF] test_mail, various: cleanup tracking tests

PR #104501

Enterprisemasterenterprise

This update enhances the tracking tests within Odoo's enterprise modules, primarily by simplifying the checks for message content and adding new tests for appointment creation. The changes streamline test maintenance and ensure consistent tracking across various modules, improving the reliability of our email tracking functionality.

Original PR description

Use higher level helper for message content check, including tracking
values. That way all checks are globally hidden in tools and it is
easier to update / adapt tests if somehow modeling of tracking values
change (yay).

Add tests for creation, which currently generates no tracking message.

Remove some duplicated / useless test or test parts when possible.

Batch-ize some tests, just to cover tracking when creating or updating
records in batch.

Update a bit duration mixin tests, trying to make them easier to
update if model has to change (yay).

Task-5503121
Prepares Task-3645865

#tracking#email#tests

[REF] stock: use only local data in stock tests WIP

PR #60381

Enterprisemasterstock

This update refactors stock tests to exclusively use local data, improving test stability and reducing reliance on external systems. This change simplifies testing and ensures consistent results, leading to more reliable stock management processes within Odoo.

#testing#stock management

[REF] whatsapp: move fields to channel

PR #104450

Enterprisemasterdiscuss

This update refactors the WhatsApp channel model and removes a previous patch related to thread management. This change streamlines the handling of data within WhatsApp channels, improving the overall system's efficiency and organization. It's a technical update focused on internal improvements to the WhatsApp functionality.

Original PR description

This commit move the fields to discuss channel model and remove thread_model_patch.

#whatsapp#channel#discuss

[REF] orm: deprecate Cache view of fields

PR #105747

Enterprisemasteresgsalesale_commissionsale_timesheet_enterprise

This update removes the use of 'Cache view of fields' within several Odoo reports. This change is part of a broader effort to streamline Odoo's codebase and improve performance. While the reports continue to function as before, this refactoring prepares for future updates and optimizations.

Original PR description

https://github.com/odoo/odoo/pull/246069

#reporting#performance#codebase

[MOV] account_accountant, *: clean up the portal chatter subfolders

PR #105775

Enterprisemasterenterprise

This update reorganizes the structure of portal chatter code to better align with how it's used across Odoo. The changes clarify which parts of the chatter system are for website-only functionality versus those shared with project sharing, improving code organization and maintainability. This ensures smoother performance and future updates.

Original PR description

When the portal chatter conversion began, code was split into `core` and `frontend` folders for chatter in portal. `core` was intended for shared logic between website and project sharing while `frontend` was reserved for website only usage.
With this commit, the boot service which is responsible for lazy loading the portal chatter in frontend is now located in the `frontend` folder.  Those that are `portal specific` or common between `portal` and `project sharing` are located in the `portal` and `portal_project` folders respectively. Accordingly, `web_portal` subfolder has been renamed to `web_portal_project` to reflect the actual usage.
The folder tree structure will look like this:

In portal:
```
src/
|-- chatter/
|   |-- frontend/
|   |-- portal/
|   |-- portal_project/
```

In mail:
```
src/
|-- chatter/
|   |-- web/
|   |-- web_portal_project/
```

[Comunity PR](https://github.com/odoo/odoo/pull/206284)

#chatter#portal#organization

Branch: 19.0

1 change

Refactoring(1)

Code cleanup and technical improvements

[REF] l10n_ar_edi: mocked test with JSON file assertions

PR #105299

Enterprise19.0l10n_ar_edi

This update streamlines the testing process for the Ar-EDI module by automatically verifying data against JSON files. Previously, tests required external modes, but now they run more reliably and easily adaptable with simple test tag adjustments. This improves the overall stability and maintainability of the Ar-EDI module.

Original PR description

This commit refactors the whole `l10n_ar_edi` test suite to use the new helpers, and made it possible for the test to (finally) be run without external mode.

Now, when running these new tests, the test framework will by default assert the request data with their associated JSON file. When a change is made, new overwrites for the test files can be easily changed by just adding the `SAVE_JSON` test tag on the command to run the tests.

task-4891206

Forward-Port-Of: odoo/enterprise#104886
Forward-Port-Of: odoo/enterprise#103370

#testing#automation#ar_edi

Use higher level helper for message content check, including tracking values. That way all checks are globally hidden in tools and it is easier to update / adapt tests if somehow modeling of tracking values change (yay). Add tests for creation, which currently generates no tracking message. Remove some duplicated / useless test or test parts when possible. Batch-ize some tests, just to cover tracking when creating or updating records in batch. Update a bit duration mixin tests, trying to make them easier to update if model has to change (yay). Task-5503121 Prepares Task-3645865

When the portal chatter conversion began, code was split into `core` and `frontend` folders for chatter in portal. `core` was intended for shared logic between website and project sharing while `frontend` was reserved for website only usage. With this commit, the boot service which is responsible for lazy loading the portal chatter in frontend is now located in the `frontend` folder. Those that are `portal specific` or common between `portal` and `project sharing` are located in the `portal` and `portal_project` folders respectively. Accordingly, `web_portal` subfolder has been renamed to `web_portal_project` to reflect the actual usage. The folder tree structure will look like this: In portal: ``` src/ |-- chatter/ | |-- frontend/ | |-- portal/ | |-- portal_project/ ``` In mail: ``` src/ |-- chatter/ | |-- web/ | |-- web_portal_project/ ``` [Comunity PR](https://github.com/odoo/odoo/pull/206284)

This commit refactors the whole `l10n_ar_edi` test suite to use the new helpers, and made it possible for the test to (finally) be run without external mode. Now, when running these new tests, the test framework will by default assert the request data with their associated JSON file. When a change is made, new overwrites for the test files can be easily changed by just adding the `SAVE_JSON` test tag on the command to run the tests. task-4891206 Forward-Port-Of: odoo/enterprise#104886 Forward-Port-Of: odoo/enterprise#103370