Tuesday, September 15, 2026
12 changes · master
Code cleanup and technical improvements
Work entry and time-off type names and codes were renamed to match Partena formats, making it easier for organizations moving from Partena to Odoo. Duplicate work entry types were cleaned up and some entries were simplified into categories for clearer payroll and absence reporting.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Point of Sale code now relies on an existing local storage mechanism for temporary order information instead of keeping a separate extra data field. This reduces duplicate storage logic and helps keep POS-related localization features easier to maintain without changing day-to-day cashier workflows.
Original PR description
Since `uiState` is also stored in `indexedDB` and can be used instead, we remove `PosOrder.extraField`. see odoo/enterprise#129862 task-6487351
Payroll work entry types have been renamed and reorganized to match Partena conventions, making it easier for Belgian payroll users to move from Partena software to Odoo. Duplicate time types were cleaned up and some entries were replaced with broader categories, improving consistency across payslips and payroll reporting.
The point of sale settlement flow now relies on already stored interface state instead of keeping a separate extra data field on orders. This reduces duplicate stored information and helps keep the payment validation process easier to maintain without changing the cashier experience.
Original PR description
Since `uiState` is also stored in `indexedDB` and can be used instead, we remove `PosOrder.extraField`. see odoo/odoo#285668 task-6487351
This updates internal editor and in-app purchase components to use the newer component property handling expected by the underlying web framework. It helps keep these areas maintainable and better validated without changing day-to-day user workflows.
Original PR description
- https://github.com/odoo/enterprise/pull/131126 See commit messages for details. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update modernizes internal component definitions used by the HTML editor, AI-assisted media tools, website sales editor integrations, and Knowledge cover dialogs. It helps keep these areas compatible with the latest interface framework and improves validation without changing user-facing workflows.
Original PR description
- https://github.com/odoo/odoo/pull/287592 See commit messages for details. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product and description information now uses Odoo's standard stacked field layout across documents such as sales, purchases, invoices, and stock moves. This reduces custom interface behavior, improves consistency, and helps avoid display issues when editing product descriptions.
Original PR description
Replace the shared `product_and_description.js` widget, used by SOL, POL, AML and stock moves, with the framework's native support for stacking multiple fields in a single column. The product and…
This update aligns accounting and helpdesk list views with a recent platform naming change. It is an internal cleanup that helps keep these screens compatible and maintainable, with no expected change to day-to-day user workflows.
Original PR description
This commit is the direct consequence of the rename of isCellReadonly into isFieldReadonly operated in https://github.com/odoo/odoo/pull/287378 due to the nature of stacked fields in list view. task-6564093
This pull request reorganizes and updates Odoo's internal ORM test models. It helps maintain product quality by making core automated tests easier to manage, with no expected direct change for everyday users.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The HR module now uses one shared method to determine an employee's reference working calendar, including for a specific date. This reduces duplicated logic and helps keep schedule-related behavior consistent across HR and payroll-related processes.
Original PR description
hr.employee._get_flexible_reference_calendar and hr.version._get_reference_calendar (added by hr_payroll) resolved a fallback calendar the same way. Move the logic to hr.version as the single _get_reference_calendar, accepting an optional date to resolve the employee's version on that date, and drop the now-unused employee-level hook. task-6569832
Payroll warning messages have been rewritten to be easier to understand and less distracting in the interface. This helps payroll users identify and resolve issues more quickly, especially in Belgian payroll workflows.
Original PR description
Warning messages from hr_payroll and l10n_be_hr_payroll module have been reformulating to increase clarity and lighten the UI. Task: 6523051
This update reorganizes how navigation item styling is handled in the web notebook component. It should not change what users see, but it reduces duplication and makes future interface fixes safer and easier to apply.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Replace the shared `product_and_description.js` widget, used by SOL, POL, AML and stock moves, with the framework's native support for stacking multiple fields in a single column. The product and description are now rendered through the `product_and_description` column using the `product_label_section_and_note_field_o2m` field. This provides product label support when available and preserves section/note handling without requiring custom product/description rendering logic. Centralize column-group visibility through `isColumnGroupFieldVisible()` and remove the custom column manipulation previously handled by `ProductNameAndDescriptionListRendererMixin`. Remove description-specific logic from `ProductLabelSectionAndNoteField` and rename the field widget to `AccountProductField`, limiting it to handling product clickability based on the current conditions. `SectionAndNoteListRenderer` continues to treat `product_and_description` as the title field, while `description_picking` retains its previous behaviour. This removes the need to render the description inside the product field, eliminating the associated `AutoResize` issues and allowing the framework to handle description rendering and column layout natively. This is the follow-up JS cleanup to the [previous PR](https://github.com/odoo/odoo/pull/273948) that removed the product name from the description (name) field. task-6241473 See also: - https://github.com/odoo/enterprise/pull/130154 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr