Tuesday, July 14, 2026
6 changes · 19.0
Enhancements to existing features
Bank reconciliation now displays draft statement lines in blue, making them easier to distinguish at a glance. This helps accounting users quickly identify items that are not yet finalized and reduces the chance of overlooking pending work.
Original PR description
This commit will put the text in blue when the statement line is in draft to be able to see quickly which lines are in draft. task-6327308
Resolved issues and error corrections
Projects linked to rental orders now show a Sales Orders count that matches the regular sales orders opened by the button. Rental orders remain available through their separate Rental Orders action, reducing confusion without hiding any records.
Original PR description
**Problem:** On a project linked to rental orders, the "Sales Orders" smart button shows a count larger than the number of orders it opens. **Steps to reproduce:** 1. Link a project to several sale…
**Problem:** On a project linked to rental orders, the "Sales Orders" smart button shows a count larger than the number of orders it opens. **Steps to reproduce:** 1. Link a project to several sale orders, some of them rental orders (e.g. 1 regular + 2 rental). 2. Open the project form: the "Sales Orders" smart button counts all of them (3). 3. Click the button. **Current behavior:** Only the non-rental orders open (1), so the count (3) does not match what is shown. **Expected behavior:** The count matches the orders the button opens (non-rental only). **Cause of the issue:** `sale_renting_project` separates the two: the "Sales Orders" action filters out rental orders (`_get_sale_orders_domain` adds `is_rental_order = False`) while rental orders get their own "Rental Orders" embedded action. But `sale_order_count` still counts every order linked to the project, rental ones included, so the button's number no longer reflects what its action opens. **Fix:** The count has to follow the same non-rental scope as the action it triggers, otherwise the button is misleading. Rental orders remain reachable through the dedicated "Rental Orders" embedded action, so excluding them from this count hides nothing. opw-6321302
When creating a project from a template, the system now matches original and copied tasks in the right order before applying scheduling calculations. This prevents dates from being copied or adjusted against the wrong task, improving reliability when using project templates.
Original PR description
Currently, `action_create_from_template` loops over both the copied and original tasks to perform the necessary datetime calculations, however, by simply zipping self.task_ids and project.task_ids, nothing guarantees the tasks are properly aligned in the loop. This can result in the original_task and copied_task being completely different. To fix this, we can sort the two recordsets by stage and sequence, which will guarantee the tasks are aligned after zipping. (provided a task was not dropped somehow) opw-6353533
Payroll pay schedule options now appear in the user's selected language across the main payroll app and multiple country-specific payroll modules. This fixes untranslated labels on employee payroll forms, improving usability for non-English users.
Original PR description
Issue: ---------------------------------------- The values of the field `schedule_pay` aren't translated. Steps to reproduce: ---------------------------------------- - Switch the language to French - Open an employee form, "Paie" tab - The selection in the "Salaire" tab is not translated to French Cause: ---------------------------------------- When the selection values were moved to a method in 7a123d71925b25f26ba0a8abff0c4a159147bdd0. The strings were not declared as translatable. opw-6359395
This change removes a reference to an employee group that does not exist in the Belgian payroll fleet setup. It helps prevent configuration errors and keeps access rules aligned with the available system groups.
Original PR description
The group hr_group_user does not exist and shouldn't be linked to these fields. task-6369268 Forward-Port-Of: odoo/enterprise#123238
The planning kanban card now shows allocated time in a simpler, consistent format such as (4h30). Removing the percentage from this spot fixes uneven spacing and makes schedule information easier to read at a glance.
Original PR description
Currently, the allocated hours and allocated percentage are misaligned in the planning kanban card, causing them to appear uneven or have inconsistent spacing. This fix removes the allocated percentage and formats the allocated hours to display like (4h30). task-5085363 Forward-Port-Of: odoo/enterprise#98776