Daily updates from Odoo
Wednesday, October 15, 2025
7 changes · saas-18.2
Resolved issues and error corrections
A regression test was added to ensure payroll work entries continue to be generated correctly when a fully flexible employee has overlapping absences, such as sick leave and a public holiday. This helps prevent a previous error from returning and improves reliability for attendance-based payroll processing.
Original PR description
**Purpose:** Add regression test to verify that overlapping leave scenarios (sick leave + public holiday) do not cause singleton errors for fully flexible employees using attendance-based work entries. **Test Coverage:** - Fully flexible employee with no calendar assignment - Attendance-based work entry source configuration - Overlapping sick leave and public holiday scenario - Work entry generation and validation without singleton errors Related : [PR](https://github.com/odoo/odoo/pull/223448) opw-4979974 Forward-Port-Of: odoo/enterprise#93902
This update prevents users from creating a new workplace directly from the contract workplace field when that shortcut could trigger an error. Users can still select existing workplaces, reducing interruptions when managing Swiss payroll contracts.
Original PR description
The _rec_name was previously set to partner_id, causing type errors when typing a new workplace name in a Many2one field. Couldn't change it to anything else, as one should have to create a new field in that stable version and this is not the best practice. As a workaround, the corresponding field in the l10n_ch_hr_contract_views.xml is removed from it the quick_create to prevent the creation of new names on the fly. task-5043056 Forward-Port-Of: odoo/enterprise#96675 Forward-Port-Of: odoo/enterprise#93424
The Shop Floor "Add Operator" action now uses the public employee list instead of private employee profiles. This prevents access warnings for users who are not allowed to view private employee data, making operator selection work smoothly while respecting privacy rules.
Original PR description
The task 4762527 added a warning for users that were not allowed to access private employee profiles. The "Add Operator" button in mrp_workorder (Shop Floor) was relying on it. I had to change their list model from hr.employee to hr.employee.public This issues was raised by Aerospacelab in the following PR: https://github.com/odoo/odoo/pull/228623 task-5156702 Forward-Port-Of: odoo/enterprise#96745
This fix ensures that views created or edited in Odoo Studio inherit from the correct primary view instead of an intermediate extension view. This helps prevent unexpected Studio customization behavior and makes view editing more reliable for users.
Original PR description
…ry view Accidentally pass an inheriting view id to edit view. Before this commit, the studio view thus created inherited from the extension view After this commit, it inherits from the closest primary view. opw-4930800 Forward-Port-Of: odoo/enterprise#96636 Forward-Port-Of: odoo/enterprise#94747
Project budget totals now use the same color logic as individual budgets, including expense budgets entered as positive amounts. This makes dashboard and project card budget indicators easier to trust and prevents misleading status colors.
Original PR description
#### Issue: - Color for project budget and total project budgets are inconsistent #### Step to reproduce: - In Settings: - activate Project > Timesheet - activate Accounting > Budget Management - Create a project - Go to Dashboard - Add a budget of type 'Expense' - Add a line with a positive amount #### Current Behavior: - Color for the budget is correct - Color for the total budget is wrong #### Expected behavior: - Color for the budget and total budget are consistent While computing budget color, expense budget are dealt as if they were negative. Therefore having a positive amount for purchase order result in some problem on the color of the total of different budgets. This commit creates temporary variables to compute progress of the global budget. Project cards in kanban view use the `total_budget_progress` field, so it also needed to be updated the same way. opw-4812468 Forward-Port-Of: odoo/enterprise#93221
This fix prevents spreadsheet list editing from breaking when a field was removed after a migration or custom field deletion. Business users can continue editing affected lists in the side panel instead of encountering a crash.
Original PR description
If a field disappeared from a list following a migration or a deleted custom field, the list could no longer be edited in the sidepanel because we tried to access the missing field info (name & string) Task-4915281 Forward-Port-Of: odoo/enterprise#96158
Installing the POS due settlement module now applies its required products to every POS setup, including those with open sessions. This prevents checkout or settlement issues caused by missing settlement, deposit, or invoice products.
Original PR description
Backport of https://github.com/odoo/enterprise/pull/95789 Before this commit, when the module pos_settle_due was installed, the special products (settle due, deposit, settle invoice) were only set on the POS configurations that did not have any open session. This could lead to issues when trying to use these products in a POS session of a configuration that did not have them set. Now, the special products are set on all POS configurations when installing the module. Community PR: https://github.com/odoo/odoo/pull/230939 Task id: 5080126