Tuesday, June 2, 2026
7 changes · master
Resolved issues and error corrections
This update fixes an issue where POS order payments incorrectly displayed negative amounts for customer balances. When a customer paid their account through a POS order, a negative 'pay_later' amount caused inaccurate calculations and inflated the 'Settle due amount' button. This ensures correct balance representation.
Original PR description
When a customer paid off their account balance through a POS order, a negative pay_later amount was used. The condition `if order_due:` in `_compute_customer_due_total` evaluated to True for negative values, causing `customer_due_total` and `init_customer_due_total` to be set to a negative amount. This made `pos_orders_amount_due` on the partner go negative, which in turn inflated `remainingDue` in the frontend (remainingDue = totalDue - posOrdersAmountDue), showing a wrong amount in the "Settle due amount" button. opw-6187771 Forward-Port-Of: odoo/enterprise#117813 Forward-Port-Of: odoo/enterprise#116394
This update fixes an issue where the Timesheet Assistant incorrectly suggested declined calendar events to users. The system now accurately includes events where the user is an attendee, regardless of their RSVP status, improving the assistant's usefulness and accuracy.
Original PR description
### Before this commit: The Timesheet Assistant would incorrectly suggest calendar events that the user had explicitly declined. Furthermore, the domain only retrieved events where the user was the organizer (`user_id`), completely missing events where the user was only an attendee. ### After this commit: The `get_calendar_events` getter in `_get_assistant_events_getters` is updated to: 1. Include events where the current user is an attendee by adding a condition on `partner_ids`. 2. Explicitly exclude events where the user's `calendar.attendee` status is 'declined'. Task-6222659 Forward-Port-Of: odoo/enterprise#117613
This update corrects a naming inconsistency in the account reports testing suite. The test function `_check_vies_iap` has been renamed to `_check_vies_validity_iap` to align with recent changes made by the community. This ensures consistent and accurate testing of account reporting functionality.
Original PR description
See commit
This update fixes a usability issue within the Timesheet Assistant by opening internal links in a modal window. This keeps users within the Timesheets Assistant menu, providing a smoother and more intuitive experience when navigating related information. It addresses a minor inconvenience for users managing their timesheets.
Original PR description
This commit opens the internal links in the custom form view displayed in the timesheet assistant inside a modal to stay in Timesheets Assistant menu. task-[6132392](https://www.odoo.com/odoo/project/4105/tasks/6132392) Forward-Port-Of: odoo/enterprise#118277 Forward-Port-Of: odoo/enterprise#114596
This update clarifies the 'invalid_scope' error message, which previously wasn't clear enough for users. The change ensures users understand why consent couldn't be granted for a specific company, improving the user experience and reducing confusion.
Original PR description
The invalid_scope error message means the user doesn't hav the legal rights to give consent for the given company. But the error message is not clear enough. This commit improve the error message clarity. task-6144883 Forward-Port-Of: odoo/enterprise#115650
This update fixes a minor issue in the DMFA report where the 'Calculation Basis' and 'Contribution Type' headers were incorrectly switched. The headers have now been corrected to their proper order, ensuring accurate reporting for payroll calculations. This ensures data consistency and reliability for financial reporting.
Original PR description
DMFA report had "Calculation Basis" and "Contribution Type" header switched. Got switched back correctly. task-6227590 Forward-Port-Of: odoo/enterprise#117740
This update fixes a bug that caused errors when date calculations involved missing or `None` offset values. The change ensures that date calculations are accurate by defaulting the offset to 0 when it's not provided, preventing unintended date movements.
Original PR description
Currently, an exception is raised when `offset` is `None` and is compared
with `MIN_OFFSET` or `MAX_OFFSET`.
Currently `offset = op.get("offset", 1)` to assign a default value of `1` when
the `offset` key was missing from `op`. However, this does not handle cases
where the `offset` key is present but its value is `None`.
This commit fixes the issue by defaulting `offset` to `0` when it is missing or
`None` in `op`. Using the default value ensures no date movement occurs
when `offset` is not explicitly provided.
Sentry-7448086997
Forward-Port-Of: odoo/enterprise#118466