Daily updates from Odoo
Saturday, November 22, 2025
9 changes
2 changes
Resolved issues and error corrections
Odoo now uses the updated official state code for Odisha in India. This helps ensure customer details and sales documents use the correct regional information and avoids mismatches when creating orders.
Original PR description
**Steps to reproduce:** 1. Install the `Contacts` module. 2. Go to Contacts > Create a new contact. 3. Select country India, and state Odisha. 4. Create a sales order using the newly created contact. **Issue:** As per [Government of India](https://www.iso.org/obp/ui/#iso:code:3166:IN), the state code was officially changed from "OR" to "OD" in 2023. However, Odoo still uses the outdated code. <img width="407" height="163" alt="image" src="https://github.com/user-attachments/assets/1631a831-f455-4a51-886f-7e4ed691add0" /> **Solution:** Update the name of the state from "OR" to "OD" in state records. **opw-4935633** Forward-Port-Of: odoo/odoo#234697
This update fixes how the mail module simulates browser settings in automated tests. It ensures the test helper is used with the right platform information, which helps keep test behavior accurate and prevents misleading results.
Original PR description
The `mockUserAgent()` is meant to be used with a "platform" ("mac",
"windows", "android"...) as parameter and not a whole user agent string.
In specific cases, a custom string can be used instead, but only to be
added to the user agent string.
This commit adapts its usage(s) accordingly.
Forward-Port-Of: odoo/odoo#2368372 changes
Resolved issues and error corrections
This update makes sure date placeholders in signing documents only appear for the signer they belong to. It prevents one signer from seeing the next signer’s placeholder, reducing confusion during the signing process.
Original PR description
Version: - saas-18.3 Steps to reproduce: - Add date fields for multiple signers. - When the first signer signs, the date placeholder for the next signer becomes visible to the first signer. Issue: - Date fields for next signers were showing placeholders to the current signer. Fix: - Added a condition to only set the placeholder when it has a valid value. Impact: - Ensures date placeholders are visible only to the correct signer. task-5218970
When a document is locked from the preview screen, the actions menu now updates immediately to show the correct options. This prevents users from seeing outdated actions and makes the document workflow more reliable.
Original PR description
Steps to reproduce =================== - Preview any documents. - Click on the actions menu and lock the document. - Now go to the actions menu again. => The set of options is not updated. Technical =========== - The action menu, which we are using inside the file previewer, is passed explicitly inside the FileViewer component of the document. We were using the `record.load()`, which will not have any effect on the FileViewer component and that's why the action menu was not updating. After this commit ================== - Used the `this._notifyChange()` method, which closes the preview and loads the model to align with the same behaviour as other actions. Task-4988116 Forward-Port-Of: odoo/enterprise#91760
2 changes
Resolved issues and error corrections
This fixes Balance Sheet report lines so they consistently apply the correct date scope when pulling figures from related reports. It helps ensure SYSCOHADA financial statements show accurate amounts for the selected reporting period.
Original PR description
Forward-Port-Of: odoo/enterprise#99889
Pay run forms in some localizations include additional fields, but their values could be lost when the record was prepared for saving or display. This fix ensures those localized fields are kept, reducing the risk of missing payroll information.
Original PR description
In some localizations, extra fields are added in the form view of payruns, these field values are lost due to the way we buildRawRecord Forward-Port-Of: odoo/enterprise#100129
3 changes
Resolved issues and error corrections
This update corrects how browser platform information is simulated in mail-related automated tests. It helps ensure the tests reflect real user environments more accurately, reducing the risk of false test results and improving reliability.
Original PR description
The `mockUserAgent()` is meant to be used with a "platform" ("mac",
"windows", "android"...) as parameter and not a whole user agent string.
In specific cases, a custom string can be used instead, but only to be
added to the user agent string.
This commit adapts its usage(s) accordingly.
Forward-Port-Of: odoo/odoo#236837This update corrects how the VoIP softphone tests simulate different devices and browsers. It helps ensure the tests behave as intended, improving reliability of future VoIP updates.
Original PR description
The `mockUserAgent()` is meant to be used with a "platform" ("mac", "windows", "android"...) as parameter and not a whole user agent string.
In specific cases, a custom string can be used instead, but only to be added to the user agent string.
This commit adapts its usage(s) accordingly.This update fixes a broken Mexican trial balance test so it matches the current chart of accounts. It also renames some UK report methods to avoid conflicts with existing UK module behavior, helping keep report functionality stable.
Original PR description
This commit fixes the Mexican trial balance unit test that was broken due to newly added accounts in Mexican CoA. It also renames methods from _get_uk_... to _get_uk_reports_... in l10n_uk_reports_cis to avoid overriding the methods in l10n_uk module. task-5176658