Saturday, May 9, 2026
4 changes · saas-19.1
Resolved issues and error corrections
This update fixes an issue where some UBL invoices were being processed incorrectly. The change ensures that invoices with a valid CustomizationID are prioritized, improving the accuracy of invoice processing. A fallback mechanism remains in place for unknown UBL formats to maintain compatibility.
Original PR description
Some UBL invoices we receive both have a node CustomizationID signifying that it's a bis3 and a UBLVersionID 2.1 (which should be illegal). We don't block malformed bis3 invoices. But we should try to guess that it's a bis3 if it has the perfect customization. We can keep the fallback in case it's an unknown bis3 format. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#263527 Forward-Port-Of: odoo/odoo#263285
This update resolves an issue where portal users couldn't see timesheets associated with tasks. The fix adjusts how timesheet visibility is determined, reflecting changes made during a recent portal system update. Now, portal users will correctly see timesheet information for shared tasks.
Original PR description
Steps to reproduce: - Install `website_timesheet` - Enable timesheets from website - Share a task with a portal user - Log in as the portal user - Open the tasks on the portal Issue: The Timesheets is not visible. Root cause: Earlier, portal card visibility and existence were controlled directly in the QWeb template. After the portal refactoring, their visibility and existence are now managed by `portal.entry` records. Fix: Determine timesheet visibility using the corresponding `portal.entry` record. task-5455588
This update fixes an issue where tax reports (specifically for GSTR2B in India) were displaying incorrect signs for bills and credit notes. The change ensures bills show positive amounts and credit notes show negative amounts, aligning with standard accounting practices and improving report accuracy.
Original PR description
In reverse charge taxes, tax tags are added on negative repartition lines, causing the amounts to appear with the opposite sign in reports. Due to this, credit notes were shown as positive amounts and bills as negative amounts. This commit fixes the sign handling so that: - bills are shown with positive amounts - credit notes are shown with negative amounts Forward-Port-Of: odoo/enterprise#116740
This update resolves an issue where a 'rotting' button was incorrectly displayed in the My Tasks Kanban view, causing a traceback. The fix corrects a misconfiguration in how the system tracks task aging, ensuring accurate reporting of overdue tasks within the Field Service app. This prevents potential confusion and ensures data integrity.
Original PR description
# How to reproduce - Go to All Tasks > All Tasks - Select the Kanban View - Edit the settings of the stage "New" - Set the value of "Days to rot" to a negative number (e.g. -4) - Go to My Tasks >…
# How to reproduce - Go to All Tasks > All Tasks - Select the Kanban View - Edit the settings of the stage "New" - Set the value of "Days to rot" to a negative number (e.g. -4) - Go to My Tasks > Tasks - Click on the red button displaying the number of task rotting # The problem We get a traceback # Cause When we click on that red, button, we call this function : https://github.com/odoo/odoo/blob/af50cb24ac536e6afb14eee8221c69906191ba2b/addons/mail/static/src/js/rotting_mixin/rotting_kanban_header.js#L11-L13 This `toggleFilterRotten` function is patched in `progressBarState` by the `RottingKanbanController` class: https://github.com/odoo/odoo/blob/af50cb24ac536e6afb14eee8221c69906191ba2b/addons/mail/static/src/js/rotting_mixin/rotting_progress_bar_hook.js#L1-L10 https://github.com/odoo/odoo/blob/af50cb24ac536e6afb14eee8221c69906191ba2b/addons/mail/static/src/js/rotting_mixin/rotting_kanban_controller.js#L6-L11 But the `FsmMyTaskKanbanController`, which the specific controller of the My Tasks view in the Field Service app does not inherit from the `RottingKanbanController` class : https://github.com/odoo/enterprise/blob/32496b52d8333f68603bba6a0c1af3ed42f59287/industry_fsm/static/src/views/fsm_my_task_kanban/fsm_my_task_kanban_controller.js#L5 Then why was the rotting button even available ? That's because `fsmMyTaskKanbanView ` inherit from `projectTaskKanbanView`, which header inherit from `RottingKanbanController` : https://github.com/odoo/odoo/blob/af50cb24ac536e6afb14eee8221c69906191ba2b/addons/project/static/src/views/project_task_kanban/project_task_kanban_header.js#L4-L9 opw-6186575 Forward-Port-Of: odoo/enterprise#116530