Odoo Changelog — 2026-09-14

Monday, September 14, 2026

2 changes · saas-18.4

Bug Fixes(2)

Resolved issues and error corrections

[FIX] project_enterprise: conflict shouldn't hit siblings

Enterprisesaas-18.4project_enterpriseMedium

Fixed an issue where one unschedulable project task could incorrectly block other tasks assigned to the same person. This helps dependent tasks reschedule to the next realistic available time instead of being pushed far into the future.

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#129326

#project#scheduling#gantt#rescheduling

[FIX] point_of_sale, pos_loyalty: exclude tips from discount

PR #287271

Coresaas-18.4point_of_salepos_discountpos_loyaltyMedium

Discount rewards in Point of Sale now exclude tip amounts, so customers' gratuities are not reduced by coupons or loyalty discounts. This keeps restaurant payments accurate and ensures staff receive the intended tip amount.

Original PR description

Currently, when a discount reward is applied onto an order and a tip is added later, the discount gets also applied on the tip. Steps to reproduce: ------------------- * Make sure all demo data…

Currently, when a discount reward is applied onto an order and a tip is added later, the discount gets also applied on the tip.

Steps to reproduce:
-------------------
* Make sure all demo data loyalty programs can also apply to the restaurant
* Make sure tipping is enabled in the restaurant
* Open restaurant
* Open a table, add items to the order
* Activate coupon code "10pc"
* Select payment
* On payment page, add a tip (10$)
* Go back to product page
> Observation: 10% discount is also applied on the tip

Why the fix:
------------
A tipping should never have a discount applied on it.

During the computation of the discountable amount we have 3 distinct flow (discount applies on the order, on the cheapest line, on some specific products)

- On the order: We always exclude tipping lines
- Cheapest line: When fetching the cheapest line amongst all lines we don't consider the tipping lines
- On specific: With the fix, tipping lines will always be excluded from the discountable lines. Even if the tip product was specified on the loyalty program. Should we still allow discounting tips if it was set in the program specifically?

We're using `is_discountable` instead for `is_tip` in case we want to extend the definition later on.

opw-6445364

Forward-Port-Of: odoo/odoo#286073
Forward-Port-Of: odoo/odoo#281400

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#129326

Currently, when a discount reward is applied onto an order and a tip is added later, the discount gets also applied on the tip. Steps to reproduce: ------------------- * Make sure all demo data loyalty programs can also apply to the restaurant * Make sure tipping is enabled in the restaurant * Open restaurant * Open a table, add items to the order * Activate coupon code "10pc" * Select payment * On payment page, add a tip (10$) * Go back to product page > Observation: 10% discount is also applied on the tip Why the fix: ------------ A tipping should never have a discount applied on it. During the computation of the discountable amount we have 3 distinct flow (discount applies on the order, on the cheapest line, on some specific products) - On the order: We always exclude tipping lines - Cheapest line: When fetching the cheapest line amongst all lines we don't consider the tipping lines - On specific: With the fix, tipping lines will always be excluded from the discountable lines. Even if the tip product was specified on the loyalty program. Should we still allow discounting tips if it was set in the program specifically? We're using `is_discountable` instead for `is_tip` in case we want to extend the definition later on. opw-6445364 Forward-Port-Of: odoo/odoo#286073 Forward-Port-Of: odoo/odoo#281400