Daily updates from Odoo
Monday, March 16, 2026
7 changes · master
Enhancements to existing features
This update resolves a discrepancy where sales projects displayed different content in the Odoo portal and PDF reports. Now, both views show the same information, ensuring a unified and accurate representation of sales projects, regardless of whether they are Field Service Management projects. This improves data consistency and user experience.
Original PR description
### In this commit: The worksheet portal displayed different content depending on whether the project was marked as Field Service. Specifically, the product recap section was hidden in the portal for non FSM projects but still appeared in the generated PDF. This commit improves the inconsistency by ensuring that both the portal view and the PDF display the same. task-4592517
Resolved issues and error corrections
This update fixes a technical issue in the Odoo Studio view editor that previously caused crashes when interacting with certain fields. The fix ensures the sidebar correctly displays information, resolving a bug related to incorrect property computations. This improves the stability and usability of the Studio interface.
Original PR description
In studio, form editor: click on a field and check the sidebr is correct Click on another field, one that has the widget many2many_tags. Before this commit, there was a crash because the internals of the sidebar were computed with the wrong props (the old ones instead of the new ones) After this commit, there is no crash opw-6004776 Forward-Port-Of: odoo/enterprise#110391 Forward-Port-Of: odoo/enterprise#110284
This update resolves an issue preventing users from successfully creating events via the Quick Create feature within the Gantt view for Dental Care appointments. The fix ensures that users can now accurately schedule events when using this common workflow. This improves the usability of the appointment scheduling process.
Original PR description
Steps to reproduce: - Go to Appointments - Dental Care -> Gantt - Quick Create an event => bug task-6037337
A recent update to the payruns module has broken the generation of demo payslips in the HK payroll system. This pull request addresses this issue, restoring the ability to create these test payslips for verification and reporting. This ensures continued functionality for testing and demonstration purposes.
Original PR description
Following recent changes on payruns, the generation of demo payslips is no longer functioning, so we need to fix it.
This update reorganizes the testing for our SEPA payment module (hr_payroll_account_iso20022) to better align with its dependencies. Previously, a test needed to rely on the Accounting module, which has now been resolved by moving the test to a new, dedicated test module dependent on Accounting. This improves the module's structure and reduces unnecessary dependencies.
Original PR description
hr_payroll_account_iso20022, which is the module supporting SEPA payments, shouldn't be dependent on Accounting, but only on Invoicing. To solve a runbot error related to a test in this module, the dependency was changed to be Accounting instead of Invoicing. After more consideration, it is instead the test that should be moved to a new test module which depends on Accounting, leaving the original module only dependent on Invoicing. Task: 5979666
This update reverts a recent change to the spreadsheet edition's testing framework. The previous update introduced issues with tests related to a style refactor. This reversion ensures the spreadsheet edition's testing remains stable and reliable.
Original PR description
This reverts commit 8f22766dac4028ce7c726a036a9ba6f7c2df2c26.
Features or functions removed from Odoo
This update removes a redundant field in the Indian Payroll module. The existing emergency contact field now adequately serves the purpose of recording relationships, streamlining data entry and reducing complexity. This change improves the user experience for Indian payroll users.
Original PR description
### Aim of this commit: - There is no point in having the `l10n_in_relationship` field in Indian Payroll. - The same purpose can still be served by writing the relationship along with the emergency contact. Example: `Emergency Contact (Father)` Task: 6008888