Sunday, September 13, 2026
3 changes · 19.0
Resolved issues and error corrections
Fixed an issue where one task that could not be scheduled correctly could cause other tasks assigned to the same person to be pushed far into the future. Project schedules should now place each task in the next suitable available slot, improving reliability when dependencies and workloads are adjusted.
Original PR description
Steps to reproduce: 1. create three tasks A,B & C with the same assignee 2. make tasks B and C depend on A and start on the `date_deadline` of task A 3. set the duration of task B (processed before C) to be longer than the 53-week search window 4. reschedule task A to end after task C starts Problem: A candidate that couldn't be scheduled was putting its assignee in conflict, subtracting the inspected availability while failing from the shared pool. Consequently, every later candidate sharing that assignee got force-placed into the same forward reschedule fallback that lands near the tail of the 53-week search window instead of the next available slot. Solution: Each candidate should be evaluated on its own ability to fit, and the time it occupies should count against the shared pool. opw-6380163 --- Forward-Port-Of: odoo/enterprise#130749 Forward-Port-Of: odoo/enterprise#129326
Ecuador invoice forms now show reimbursement details only to users with the right accounting permissions. This prevents non-accounting users from seeing access errors when opening invoices, improving day-to-day reliability without changing invoice data.
Original PR description
The reimbursement lines are added to the invoice form without any group restriction, while their model can only be accessed by accounting users. As a result, opening an invoice form as a user without accounting rights can raise an AccessError when the form view tries to retrieve the reimbursement subview. This commit restricts the reimbursement page to the groups allowed to access reimbursement lines. [error-946579](https://runbot.odoo.com/odoo/error/946579) Forward-Port-Of: odoo/enterprise#129981
This change updates PINT e-invoicing to use the newer UBL export flow instead of the older BIS 2.0 process. It helps align invoice exports with the current standards and supports the planned removal of legacy BIS implementation.
Original PR description
Problem --------- Currently, PINT uses the old BIS2.0 export. Objective --------- Decouple the exports as an effort to remove the old BIS implementation. no-task --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#283585