Monday, February 23, 2026
4 changes · saas-18.4
Resolved issues and error corrections
This update resolves an issue where users within the 'Planning / User' group couldn't take open shifts. The fix ensures that the 'I Take It' button is displayed correctly for these users, allowing them to seamlessly accept shifts within the Planning app. This improves the usability of the Planning feature for all users.
Original PR description
## Issue In the Planning app, users within the *Planning / User* groups could not take open shifts. The button *"I Take It"* would not be displayed when clicking on the shift. ## Steps to reproduce…
## Issue
In the Planning app, users within the *Planning / User* groups could not take open shifts. The button *"I Take It"* would not be displayed when clicking on the shift.
## Steps to reproduce
1. Install the *Planning* (`planning`) app
2. In the Planning app, as an admin, create and publish an open shift
3. Log in as a *User*, open the *Planning* app, and click on the open shift
4. **The _"I Take It"_ button is not displayed**
When logging in as a user who is **not** part of the *Planning / User* group, the *I Take It* button is displayed.
## Cause
The condition for the *I Take It* button to be displayed is the following:
https://github.com/odoo/enterprise/blob/301e3c40c3272a6ae89a1eb4387d7d244e1dc52c/planning/views/planning_views.xml#L282-L283
The condition that makes the button invisible is `not context.get('my_planning_action')`. When the user is part of *Planning / User*, the schedule they see when opening the *Planning* app is the *"Schedule by Resource"*, which has the following context:
https://github.com/odoo/enterprise/blob/301e3c40c3272a6ae89a1eb4387d7d244e1dc52c/planning/views/planning_views.xml#L716
When a user who **is not** part of the *Plannig / User* group opens the *Planning* app, they see their own schedule, where the context is different than in the first case:
https://github.com/odoo/enterprise/blob/301e3c40c3272a6ae89a1eb4387d7d244e1dc52c/planning/views/planning_views.xml#L636
Because the `my_planning_action` property is in the context (and all the other conditions are respected), the button is displayed.
opw-5451282
Forward-Port-Of: odoo/enterprise#104919This update corrects a previous issue where GL reports were incorrectly filtering based on AML labels instead of account names. Previously, searching for an account wouldn't always return the correct lines. This change ensures GL reports accurately filter by the specified account name, improving report accuracy and usability.
Original PR description
Since 235a5160d13296328b79e4092a8b88a733628268, the GL reports line names are set from the amls name instead of the account name. This leads to wrong behavior when trying to filter the GL, either by using the search bar or opening the GL from a P&L line. Steps: - Create a move with a line using account 442000 for example - Create another move with no line using 442000 account - Set label of one line to be containing "442000" - Go to GL and input '442000' in the search bar -> The line with label '442000' in displayed This commit set the report line's name from the account name instead of the aml's name opw-5070801
This update resolves an issue where data related to Dian tax calculations (l10n_co_dian) was being reset unexpectedly. The fix ensures that key data elements are properly flushed, maintaining accurate accounting records for users in Colombia. This improves the reliability of financial reporting.
Original PR description
task-5500236
This update resolves a validation error occurring during invoice tax calculation with the Avatax service. The issue stemmed from incorrect tax data being sent, leading to calculation discrepancies. This fix ensures accurate tax calculations for BR localization invoices.
Original PR description
Steps to reproduce: - Set up a Company with BR localization - Create a product as follows: - [General Information] Product Type: Service - [Sales] LC116 Code: 14.01 - [Sales] Purpose of Use: Not applicable - [Sales] Service Code Origin: 14.01.3/168061/1524 - [Sales] Service Codes: 14.01.3/168061/1524 - Create an Invoice with Document Type "Electronic Service Invoice - NFS-e" - Add the product on the line - Compute taxes - Compute taxes again Issue: Action will be blocked by a validation error resulting from the external taxes call ``` odoo.exceptions.ValidationError: Odoo could not fetch the taxes related to Draft Invoice. Errors: Rejection: Total Installments doesnt match Total Lines ∑ installments[m]grossValue - ∑ (lines[n].lineAmount-line[n].lineTaxedDiscount) <> 0 ``` It occurs because during the call the system is considering the existing taxes on the line and it will send to the avatax service wrong amounts opw-5412456 opw-5409735