Daily updates from Odoo
Monday, January 12, 2026
8 changes · master
Resolved issues and error corrections
A bug was causing errors when switching between the Timesheet grid view and stopping timers, due to sample data incorrectly reflecting running times. This update ensures all sample timesheets have their timers paused, resolving the issue and improving the stability of the Timesheet grid.
Original PR description
Steps to reproduce: - Open Timesheets app, - Click on search(magnifying lens) to open on cell with no records. - Let sample record be loaded. Issue: - Timer is already started. If you switch back to grid view and stop the time it throws traceback as it has data of sample records. Reason: - The sample records can have record states that are running. Fix: - Make sure all the sample records created have their timer paused using field `is_timer_running`. - Update condition in time display to check if time is running instead using `is_timer_running` not using `time_start` and `time_pause` as `time_pause` is not an active field. task-5267303 Forward-Port-Of: odoo/enterprise#102035
This update corrects a display issue on the website related to subscription products. Previously, the delivery period was shown in English, regardless of the user's language setting. This fix ensures that the delivery period is now correctly translated into the user's preferred language, improving the customer experience.
Original PR description
This commit[^1] introduced a "Deliver Every [period]" text on the website for subscription consumable products, but used the raw selection key that was not translated. As a result, people would see only the "Deliver Every" part in their language, and the period in English. To fix this, we added a computed field with a properly translatable string that is used on the website. Issue reported by support. [^1]: https://github.com/odoo/enterprise/commit/beb7238882eda1fd36aa22bdb6441b8bd5556ef3 Forward-Port-Of: odoo/enterprise#103645
This update prevents users from deleting visitors who are currently Checked-In or Checked-Out, safeguarding visitor tracking data and ensuring accurate records. The system now displays a 'Set as Planned' button for these visitor states and provides a clear error message if deletion is attempted. This improves data integrity and operational efficiency.
Original PR description
Purpose: - The purpose of this change is to prevent accidental deletion of visitors who are currently Checked-In or Checked-Out, ensuring data integrity and proper tracking of visitor activity. This PR includes: - Prevented deletion of visitors unless they are in Planned or Cancelled state. - Added a clear error message when deleting Checked-In or Checked-Out visitors. - Displayed the 'Set as Planned' button for Checked-In, Checked-Out, and Cancelled states. - Added test cases for visitor deletion restrictions. task-5380323
This update resolves a technical error that was preventing users from correctly accessing and editing sign templates linked to certain templates. The fix corrects record rules within the sign.item.role module, ensuring proper access rights are enforced. This improves the usability and reliability of the sign template functionality.
Original PR description
Fix record rules on sign.item.role that prevented users from reading and creating item roles linked to accessible templates, causing access errors when opening or editing sign templates. task-5428886
This update corrects a problem with importing WinBooks tax data. Previously, the import process incorrectly included tax tags with signs, leading to inaccurate tax reporting. This change removes the sign from tax tags during import, ensuring correct tax calculations and reporting.
Original PR description
Import a WinBooks file on a fresh database (a sample can be found in the test files of test_winbooks_import). In the imported taxes, we can see that the tax_tags contain signs. However, since https://github.com/odoo/odoo/pull/225252 , tax tags should no longer store a sign. This causes issues with imported entries in the tax reports: they are not included. This commit adapts the import for WinBooks tax_tags to remove their sign before importing them. opw-5345933 Forward-Port-Of: odoo/enterprise#103691 Forward-Port-Of: odoo/enterprise#101459
This update adjusts how taxes are processed on sales orders and invoices, specifically aligning with fiscal position requirements. Previously, taxes not directly linked to the fiscal position were retained; now, they are automatically removed. This change ensures accurate reporting and compliance with tax regulations, primarily impacting financial reporting modules.
Original PR description
In linked community commit, if a tax is set on a sale order or invoice, and the tax is not an original or replacement tax on the fiscal position of the SO or invoice, the tax is removed. Therefor : - Addapt nl xaf & gt test cases to reflect FP behavior change. Tests had a case where : > a tax_a with fiscal_pos_a, > a tax_b with fiscal_pos_b replace tax_a, > an invoice with fiscal_pos_a with a line with taxes tax_a & tax_b. Before both taxes were kept, now tax_b is removed. As we see no reason to support the previous behavior, the expected result of the test is changed. - Update cls.tax_sale_b fp in TestGtFlow to prevent removal of tax_sale_b Task: 5017278
This update removes a confusing field from the payment report generation process. Previously, a separate 'Payment Date' was required, leading to user confusion when creating payment advice reports. Now, standard payment dates are used, streamlining the reporting process and improving clarity.
Original PR description
Before: * Generate Payment report wizard showed a separate Payment Date field. * This caused confusion when generating payment advice reports. After: * Removed the Payment Date field from the localization Generate Payment report wizard. task-5443068
This update fixes a naming inconsistency within the Odoo Enterprise system. The 'acc_number' field on the res.partner.bank was renamed to 'account_number' to align with standard naming conventions. This ensures data accuracy and simplifies future system updates.
Original PR description
'acc_number' res.partner.bank field was renamed 'account_number' See: https://github.com/odoo/odoo/commit/113d77eb35aa8f8b503043d1201b6cdf78e9be83#diff-22e97cf61c6826e67cd9a3276bdb292e997cb1117ca44c1749c69d5d01931787