Odoo Release Updates
Every commit to Odoo Community and Enterprise, parsed and categorized. Never miss a bug fix, improvement, or new feature.
Activity
2026-04-09
2026-04-05
2026-04-03
[IMP] *: use widget "boolean_checkbox" to have checkbox on small screen
[IMP] hr: enhance employee type model with DIMONA category and worker code
2026-04-02
2026-04-01
2026-03-31
2026-03-30
2026-03-27
[IMP] mail: add internal field option to Store fields
2026-03-25
This commit introduces a new _access_domain method to replace custom _check_access implementations, making record-level access rules explicit and visible in ir.rule definitions rather than hidden in code overrides. The change converts complex access logic from Python methods into computed user-dependent domain fields (res_access_read, res_access_write, etc.) on mail models, enabling record rules to work consistently across all access flows while allowing models that inherit from attachments or mail to selectively bypass inherited access rules.
[IMP] orm: access_domain and explicit record rules
2026-03-24
This commit fixes a critical traceback that occurred when internal users started live chat conversations with the hr_holidays module installed. The root cause was unsafe access to user.activeCompany in the employee_id computed field, which is not available in the frontend session. The fix adds optional chaining (?.) to guard against undefined activeCompany, reorganizes asset bundles for better modularity, and adds comprehensive test coverage including a new shared embed test that validates the scenario works with HR employee records present.
[FIX] hr, *: prevent traceback when starting live chat as internal user
2026-03-23
This commit applies a systematic OWL3 migration across the entire Odoo codebase by prefixing all template variable references with "this." to comply with upcoming OWL3 requirements. In OWL3, component instance properties must be explicitly accessed via "this." in templates, changing from implicit scope resolution to explicit context binding. This large-scale automated refactoring affects template files across multiple modules including account, board, CRM, HR, and many others, converting patterns like "showUploadButton" to "this.showUploadButton" and "state.name" to "this.state.name" throughout XML templates.
[IMP] *: run rendering context migration script entire codebase
This commit consolidates avatar card handling across HR modules by centralizing the single source of truth for employee information in hr.employee records rather than duplicating data across multiple models. The hr.employee.public model is now simplified to act as a proxy to hr.employee using access control, eliminating duplicate field definitions and complex JavaScript patches. The store service's employee chat lookup is refactored to use the standard Store API instead of maintaining a separate employee cache, improving consistency and reducing code complexity.
[REF] mail, *: clean up avatar card and related models
2026-03-20
This refactoring removes the 'archive' presence state from the HR module since it provided little practical value, and instead hides the presence status icon entirely when an employee is archived. The change simplifies presence state management by eliminating redundant state tracking while still preventing display of presence information for inactive employees, addressing usability issues where archived employee status was being confused with actual presence states.
[REF] hr: remove archive option from presence, hide icon when employee archived
2026-03-19
[REF] *: run rendering context migration script again
[REF] web: add this. in rendering context
2026-03-18
[REF] web: add this. in rendering context
2026-03-17
[REF] *: migrate type="base64" to "bytes"