Saturday, March 28, 2026
4 changes · 19.0
New functionality added to Odoo
This update adds a necessary report handler to the TDS-TCS (IT Act 25) reports within Odoo Enterprise. This ensures that these reports, which are required for compliance with Indian tax regulations, can now be generated correctly. This change supports ongoing tax reporting requirements.
Original PR description
With this commit, the report handler will be added to TDS-TCS (IT Act 25) reports. task-6035844
Resolved issues and error corrections
This update fixes a leak in automated web tests by ensuring audio-related event listeners are cleaned up after each test. It helps keep test runs stable and prevents leftover test data from affecting later checks.
Original PR description
Forward-Port-Of: odoo/odoo#256376
This fixes an issue where translated values could be lost from the system cache when related fields were updated during onchange processing. It helps ensure computed fields continue to use the correct language values, reducing inconsistent multilingual behavior for users.
Original PR description
when related translated field (field_x) is changed when onchange, if another computed fields which depends on the field_x is recomputed but using another language value of the field_x. The orm should keep the existing translations in the cache but not drop them. 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#256324 Forward-Port-Of: odoo/odoo#256111
This fix makes the automated test for sales EDI document dates use the same source date as the generated export. It prevents false test failures around midnight in different time zones, helping keep EDI export validation stable.
Original PR description
The Issue: Before this commit, the generated EDI XML used `sale_order.create_date.date()` to populate the IssueDate node, while the test used `datetime.today().date()` to build the expected value. Since `create_date` is a UTC timestamp set by the database and `datetime.today()` returns the local system time, these diverge when the server timezone is ahead of UTC and the test runs shortly after local midnight (e.g., runbot at 01:00 CET produces UTC date Jan 11 vs local date Jan 12). The Fix: Align the test to derive its expected date from `so.create_date.date()` instead of `datetime.today().date()`, ensuring both sides use the same timezone-consistent source of truth. runbot-237841 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#256065