Odoo Changelog — 2026-03-02

Monday, March 2, 2026

5 changes · saas-18.2

Bug Fixes(5)

Resolved issues and error corrections

[FIX] documents_hr: allow to share hr documents to employees without user

Enterprisesaas-18.2documents_hr

This update resolves an issue where HR document sharing links wouldn't work for employees without a user account. The fix ensures that documents can be shared correctly, even when an employee leaves the company, streamlining the offboarding process.

Original PR description

purpose: when an employee leaves the company, it's expected to send the HR Documents Access Link. But, an error occurs if the employee is not linked to a user.

fix:
- made the error appear only when the employee doesn't have a private email and not depend on the employee being linked to a user
- made the documents check for `work_contact_id` to get the partner related to the employee instead of `user_partner_id`

task-id: 5876084

Forward-Port-Of: odoo/enterprise#105652

#HR#Documents#Employee Offboarding

[FIX] planning, resource, hr_attendance_gantt: return no gantt unavailabilities for flexible calendar

PR #108937

Enterprisesaas-18.2planninghr_attendance_ganttMedium

This update fixes an issue where employees with flexible calendars displayed incorrect grayed-out days in planning and related modules. The change ensures that flexible employees are only unavailable on public holidays, improving the accuracy of scheduling and resource allocation. This resolves a visual discrepancy impacting how employees see their availability.

Original PR description

### Issue: When an employee has a flexible calendar, its gantt view in planning and other modules, like project or time off, shows incorrect grayed-out days. In general, employees with a flexible…

### Issue:
When an employee has a flexible calendar, its gantt view in planning and other modules, like project or time off, shows incorrect grayed-out days. In general, employees with a flexible calendar should not have any grayed out days other than public holidays.

### Steps to reproduce:
- Create a new work schedule:
    - Flexible Hours
    - 24 hours per week
    - 8 average hours per day
- Create an employee with this work schedule
- Open Planning app
- Only the three first days of the week are not grayed out

### Cause:
With 24 hours per week, the worked time can be done in three days. Odoo considers that the first three days of the given time frame are worked, but the others aren't. This result is returned by `_work_intervals_batch()`. In `_unavailable_intervals_batch()` we then build the unavailabilities by taking the inverse of the work intervals. The only exception was for fully flexible resources (i.e. without a calendar).

### Solution:
The case we need to consider is for flexible resources: they are available anytime, all week long except on public holidays and leaves.

To do this we fix the method `_unavailable_intervals_batch()` which is then called by each module. If the resource is flexible, then we only return the interval of the public holidays overlapping with the time frame.

Works in `appointment`, `hr_holiday_gantt`and `project_enterprise`.

In `planning`, we need to skip the case where nothing is returned in `leaves_mapping` otherwise it will consider the `company_leaves` during weeks with no public holiday or leaves.

In `hr_attendances_gantt`, `_unavailable_intervals_batch()` is not called. So we change the way the unavailabilities were computed to call `_unavailable_intervals_batch()` instead.

Forward-Port-Of: odoo/enterprise#105521

[FIX] l10n_mx_edi: Prevent sending PUE payments to CFDI

PR #109105

Enterprisesaas-18.2l10n_mx_ediMedium

This update corrects an issue where payments for invoices paid within 30 days (PUE) were incorrectly sent to the Mexican tax authority (CFDI). By disabling a specific function, we now ensure that only payments meeting the required 30-day term are processed for CFDI submission, improving compliance and accuracy.

Original PR description

Issue:
Sending PUE payments to CFDI/SAT is no more suitable

Step to reproduce:
- In a Mexican company
- Create an invoice (Invoice A)
- Add a line
- Set Payment Terms to "Immediate payment"
- Confirm
- Duplicate (Invoice B)
- Confirm
- Duplicate again (Invoice C)
- Set Payment Terms to "30 days"
- Confirm
- Go to Invoice A
- Pay it. It should appear as "Paid"
- Send it to CFDI
- Go to Accounting > Customer > Invoices
- Select Invoice B and C
- Pay and select the "Group Payments". They should appear as paid.
- In every invoice, click the "Update Payment" button

Current behavior:
- In Invoice A -> Sheet CFDI: A button "Force CFDI" allow sending the payment to CFDI
- In Invoice B/C -> sheet CFDI: Click on the "Download" part of the Payment line, the XML that was sent to CFDI include both invoice B and C

Expected behavior:
- It shouldn't be possible to send payment for invoice A to CFDI.
- Payment for invoice B shouldn't be sent to CFDI

Cause:
Payment for invoice paid in less than 30 days, referred as PUE, shouldn't be sent to CFDI.

Solution:
Disable the force sending to CFDI

About tests:
l10n_mx_edi_cfdi_invoice_try_update_payments already send payment to CFDI for PPD invoices. Calling action_force_payment_cfdi was pointless and causing a mess.

opw-5381600

Forward-Port-Of: odoo/enterprise#108932
Forward-Port-Of: odoo/enterprise#104628

[FIX] sign: fix wrong binding model for Activity Logs report

PR #109171

Enterprisesaas-18.2sign

The Activity Logs report was incorrectly appearing in the Sign Template list view, causing errors. This fix corrects a misconfiguration in the report's model settings, ensuring it now displays correctly within the Sign Request view. This improves report accessibility and prevents technical errors.

Original PR description

Version:
- saas-18.2

Issue:
- The "Activity Logs" report was showing in the Sign Template list view. When clicking it, a traceback occurred because the report tried to read a `sign.request` record from a `sign.template` context.

Cause:
- The report model was set to `sign.request`, but the`binding_model_id` was set to `model_sign_template`.
- This mismatch caused the report to appear in the wrong place.

Solution:
- Updated the `binding_model_id` to `model_sign_request` so the report now appears in the Sign Request view, which matches the report model and prevents the error.

task-5984137

#reporting#sign#activity logs

[FIX] web_gantt: remove snapping logic from pill name computation

PR #109217

Enterprisesaas-18.2web_ganttMedium

This update fixes an issue where shift hours weren't accurately displayed in Gantt charts when shifts spanned over two days and were less than 3 hours. The previous logic incorrectly truncated pill names. Removing the outdated snapping logic ensures accurate hour representation for all shifts, improving planning accuracy.

Original PR description

### Issue: The pill name contains the hours when it spans over the next day for less than 3 hours but not if more than 3 hours. ### Steps to reproduce: - Go to Planning app - Create a shift for an…

### Issue:
The pill name contains the hours when it spans over the next day for less than 3 hours but not if more than 3 hours.

### Steps to reproduce:
- Go to Planning app
- Create a shift for an employee from 3pm to 2am (over two days)
- The hours of the shift are displayed
- Modify the shift end to 3am
- The hours of the shift aren't displayed

### Cause:
Before the refactor adapting the gantt view to OWL, when a shift spanned over two days less than three hours, then the gantt view truncated the pill to display it in only one day. (see [`_snapToGrid()`](https://github.com/odoo/enterprise/blame/a16b2ef569903c0ae5803c169dbd68acd0141fe1/web_gantt/static/src/js/gantt_row.js#L1044-L1072)) The same logic was done for the computation of the pill's name in [this commit](https://github.com/odoo/enterprise/commit/98a86cbacf484646f486e4648788cfa53cc9648c).

But as the pills are no longer truncated since 17.0, the computation of pill names is faulty.

### Solution:
We remove the checks of the 3-hour margin. This also makes the variable `spanMoreThanOneDay` useless, so we delete it.

opw-5881532

Forward-Port-Of: odoo/enterprise#108897
Forward-Port-Of: odoo/enterprise#107233

purpose: when an employee leaves the company, it's expected to send the HR Documents Access Link. But, an error occurs if the employee is not linked to a user. fix: - made the error appear only when the employee doesn't have a private email and not depend on the employee being linked to a user - made the documents check for `work_contact_id` to get the partner related to the employee instead of `user_partner_id` task-id: 5876084 Forward-Port-Of: odoo/enterprise#105652

### Issue: When an employee has a flexible calendar, its gantt view in planning and other modules, like project or time off, shows incorrect grayed-out days. In general, employees with a flexible calendar should not have any grayed out days other than public holidays. ### Steps to reproduce: - Create a new work schedule: - Flexible Hours - 24 hours per week - 8 average hours per day - Create an employee with this work schedule - Open Planning app - Only the three first days of the week are not grayed out ### Cause: With 24 hours per week, the worked time can be done in three days. Odoo considers that the first three days of the given time frame are worked, but the others aren't. This result is returned by `_work_intervals_batch()`. In `_unavailable_intervals_batch()` we then build the unavailabilities by taking the inverse of the work intervals. The only exception was for fully flexible resources (i.e. without a calendar). ### Solution: The case we need to consider is for flexible resources: they are available anytime, all week long except on public holidays and leaves. To do this we fix the method `_unavailable_intervals_batch()` which is then called by each module. If the resource is flexible, then we only return the interval of the public holidays overlapping with the time frame. Works in `appointment`, `hr_holiday_gantt`and `project_enterprise`. In `planning`, we need to skip the case where nothing is returned in `leaves_mapping` otherwise it will consider the `company_leaves` during weeks with no public holiday or leaves. In `hr_attendances_gantt`, `_unavailable_intervals_batch()` is not called. So we change the way the unavailabilities were computed to call `_unavailable_intervals_batch()` instead. Forward-Port-Of: odoo/enterprise#105521

Issue: Sending PUE payments to CFDI/SAT is no more suitable Step to reproduce: - In a Mexican company - Create an invoice (Invoice A) - Add a line - Set Payment Terms to "Immediate payment" - Confirm - Duplicate (Invoice B) - Confirm - Duplicate again (Invoice C) - Set Payment Terms to "30 days" - Confirm - Go to Invoice A - Pay it. It should appear as "Paid" - Send it to CFDI - Go to Accounting > Customer > Invoices - Select Invoice B and C - Pay and select the "Group Payments". They should appear as paid. - In every invoice, click the "Update Payment" button Current behavior: - In Invoice A -> Sheet CFDI: A button "Force CFDI" allow sending the payment to CFDI - In Invoice B/C -> sheet CFDI: Click on the "Download" part of the Payment line, the XML that was sent to CFDI include both invoice B and C Expected behavior: - It shouldn't be possible to send payment for invoice A to CFDI. - Payment for invoice B shouldn't be sent to CFDI Cause: Payment for invoice paid in less than 30 days, referred as PUE, shouldn't be sent to CFDI. Solution: Disable the force sending to CFDI About tests: l10n_mx_edi_cfdi_invoice_try_update_payments already send payment to CFDI for PPD invoices. Calling action_force_payment_cfdi was pointless and causing a mess. opw-5381600 Forward-Port-Of: odoo/enterprise#108932 Forward-Port-Of: odoo/enterprise#104628

Version: - saas-18.2 Issue: - The "Activity Logs" report was showing in the Sign Template list view. When clicking it, a traceback occurred because the report tried to read a `sign.request` record from a `sign.template` context. Cause: - The report model was set to `sign.request`, but the`binding_model_id` was set to `model_sign_template`. - This mismatch caused the report to appear in the wrong place. Solution: - Updated the `binding_model_id` to `model_sign_request` so the report now appears in the Sign Request view, which matches the report model and prevents the error. task-5984137

### Issue: The pill name contains the hours when it spans over the next day for less than 3 hours but not if more than 3 hours. ### Steps to reproduce: - Go to Planning app - Create a shift for an employee from 3pm to 2am (over two days) - The hours of the shift are displayed - Modify the shift end to 3am - The hours of the shift aren't displayed ### Cause: Before the refactor adapting the gantt view to OWL, when a shift spanned over two days less than three hours, then the gantt view truncated the pill to display it in only one day. (see [`_snapToGrid()`](https://github.com/odoo/enterprise/blame/a16b2ef569903c0ae5803c169dbd68acd0141fe1/web_gantt/static/src/js/gantt_row.js#L1044-L1072)) The same logic was done for the computation of the pill's name in [this commit](https://github.com/odoo/enterprise/commit/98a86cbacf484646f486e4648788cfa53cc9648c). But as the pills are no longer truncated since 17.0, the computation of pill names is faulty. ### Solution: We remove the checks of the 3-hour margin. This also makes the variable `spanMoreThanOneDay` useless, so we delete it. opw-5881532 Forward-Port-Of: odoo/enterprise#108897 Forward-Port-Of: odoo/enterprise#107233