Daily updates from Odoo
Tuesday, May 19, 2026
9 changes
2 changes
Enhancements to existing features
This update enhances the Windows IoT version tracking by automatically recording the build date in a VERSION file, mirroring the format used for Raspberry Pi IoT images. This ensures consistent versioning and simplifies identifying the specific build of the IoT installation. Additionally, the Windows version is now logged upon startup for easier monitoring.
Original PR description
Before this commit, the Windows IoT version was hardcoded to '23.11'. After this commit, the installer now writes a VERSION file to the IoT install directory (which will remain between git checkouts). This file contains the build date in `YYYY.MM.DD` format, the same as the current Raspberry Pi IoT images. In addition, the Windows version is now logged on startup. task-6196801 **Image version:** <img width="306" height="39" alt="image" src="https://github.com/user-attachments/assets/f0252d44-4b5c-4bb5-aac8-4b8f56dc6ee2" /> **Windows version:** > INFO ? odoo.addons.iot_drivers.main: Windows version: Windows-11-10.0.26100-SP0 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#263392 Forward-Port-Of: odoo/odoo#263089
This update ensures that new fields added to the planning slot template – specifically company ID and worksheet template ID – are thoroughly tested. These tests were created to maintain code quality and prevent potential issues related to these template configurations within the Odoo Enterprise system.
Original PR description
The purpose of this commit is to ensure that the code of the following PR: https://github.com/odoo/enterprise/pull/112198 is properly tested. We add tests related to the addition of the `company_id` field on planning.slot.template, as well as the addition of `worksheet_template_id` field. task-6147827
2 changes
Enhancements to existing features
This update enhances the Windows IoT version tracking by automatically recording the build date in a VERSION file. This ensures consistent version identification across installations and simplifies troubleshooting. The Windows version is also now logged on startup for easier monitoring.
Original PR description
Before this commit, the Windows IoT version was hardcoded to '23.11'. After this commit, the installer now writes a VERSION file to the IoT install directory (which will remain between git checkouts). This file contains the build date in `YYYY.MM.DD` format, the same as the current Raspberry Pi IoT images. In addition, the Windows version is now logged on startup. task-6196801 **Image version:** <img width="306" height="39" alt="image" src="https://github.com/user-attachments/assets/f0252d44-4b5c-4bb5-aac8-4b8f56dc6ee2" /> **Windows version:** > INFO ? odoo.addons.iot_drivers.main: Windows version: Windows-11-10.0.26100-SP0 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#263392 Forward-Port-Of: odoo/odoo#263089
This update simplifies how Odoo manages add-on locations. It now supports using wildcard patterns in the list of add-on paths, making it easier to manage multiple Odoo installations from a single root. This reduces the need for manual configuration and streamlines add-on deployment.
Original PR description
Pass all addons_path entries through glob.glob(), which returns [path] for literal paths and expands patterns otherwise. This is useful when managing multiple Odoo repositories under a common root, avoiding the need to list each addons path explicitly. Forward-Port-Of: odoo/odoo#259690
1 change
Enhancements to existing features
This update simplifies how Odoo manages addon locations. It now supports using wildcard patterns (globbing) in the list of addon paths, making it easier to manage multiple Odoo installations. This change reduces the need for manual configuration and improves flexibility for developers.
Original PR description
Pass all addons_path entries through glob.glob(), which returns [path] for literal paths and expands patterns otherwise. This is useful when managing multiple Odoo repositories under a common root, avoiding the need to list each addons path explicitly. Forward-Port-Of: odoo/odoo#259690
4 changes
Enhancements to existing features
This update enhances the user experience of the Odoo portal by standardizing the capitalization of chatter headers. Additionally, the chatter header has been moved to its template, streamlining the design and making future updates easier. This improves consistency and maintainability of the portal interface.
Original PR description
* = planning_field_service, sign Community PR: https://github.com/odoo/odoo/pull/255516 This commit improves the portal chatter UX by adapting the capitalization of the chatter header. This commit also moves the portal chatter header to its template, reducing repetitions and making it easier to adapt in the future. task-6041769
This update removes restrictions on the fiduciary VAT field in the connection wizard for the Codabox BE localization module. This change provides greater flexibility for users managing fiduciary VAT settings, streamlining the connection process. It addresses a previous limitation impacting VAT configuration.
Original PR description
This commit will remove the readonly on the fiduciary_vat in the connection wizard. It will give more flexibility for fiduciary. task-6148930 Forward-Port-Of: odoo/enterprise#115752
This update cleans up the action menu within the Sales Order module, streamlining the user experience. The action's name has been updated for clarity and consistency. This change improves the overall usability of the sales order process.
Original PR description
In the Action menu (accessed via the gear icon), action has been renamed. Community PR: https://github.com/odoo/odoo/pull/257925 tasks-6088366
This update allows timesheet managers to approve their own timesheets, streamlining the approval process for self-managers. This change simplifies workflow and reduces the need for manual intervention when a manager approves their own work. It's a minor improvement to the timesheet management system.
Original PR description
Timesheet managers can approve their own timesheets if they have access to all timesheets and they assigned themselves as their timesheet approver task-4755604