Daily updates from Odoo
Wednesday, June 10, 2026
2 changes
Code cleanup and technical improvements
This update modernizes how Odoo Enterprise references documents and other data by transitioning to Owl 3's signal system. This change improves the underlying architecture and ensures compatibility with future Odoo releases. It impacts several key modules within the Enterprise edition.
Original PR description
## `t-ref` string refs → Owl 3 signals (enterprise companion) Enterprise side of the Owl 2 → Owl 3 ref-semantics migration. Pairs with the community PR of the same branch name (`master-tref-pr-5-nby`). ### Scope **Leaf 3** companion — `documents` `useNestedSortable`, datetime, call-card `useHover` consumers. ### Notes - Rebased onto current enterprise `master` (2026-06-10). - Community PR: odoo/odoo#269268
This update refactors the connection between overtime records and employee attendance, improving data accuracy and efficiency. Previously, a workaround was used, but this commit establishes a proper Many2One relationship, aligning with best practices and simplifying future maintenance. This change enhances the reliability of attendance tracking.
Original PR description
In odoo/odoo#241457 we made the relationship between overtime and attendance a m2o
using time_start and employee_id as keys to attribute an overtime to its attendance.
This wasn't ideal but was what was possible with the stable policy. In this commit we
complete that fix by changing the relationship to a proper Many2One.
task-6172452