Monday, June 2, 2025
4 changes · saas-18.2
Resolved issues and error corrections
A country-specific payroll localization was excluded from a broad accounting localization test because it was causing the test suite to fail. This keeps automated checks stable while the underlying localization issue can be handled separately, reducing disruption to development and releases.
Original PR description
The `all_l10n` standalone test started to fail on 2025-06-01 when installing `l10n_in_hr_payroll`.
The document action menu no longer shows Export or Insert in spreadsheet when they are not relevant for the selected document. This reduces confusion and helps users focus on the actions that actually apply in Documents.
Original PR description
Before this commit: - Select any document. - Click the SERVER ACTIONS cog menu. - You will find the menus --> `Export` and `Insert in spreadsheet` Issue: - These are not required here. Reason: - A recent PR (https://github.com/odoo/enterprise/pull/77329) changed how certain server actions are displayed when a document is selected. Fix: - We override the function returning the Dropdown Items to display and simply pop the ones we don't need. Task-4743029
Invalid demonstration data in the India payroll module was disabled so localization tests can complete successfully. This helps keep payroll-related installations stable without changing business functionality for users.
Original PR description
The `all_l10n` standalone test started to fail on 2025-06-01 when installing `l10n_in_hr_payroll`. A first attempt was made to blacklist the module in the test itself. This attemps failed as the module is auto_install on `hr_payroll` and most of `l10n_hr*` modules depend on `hr_payroll`.
Corrected an internal test expectation for the Appointment HR module so automated checks pass reliably. This helps keep future updates moving smoothly without affecting day-to-day user workflows.
Original PR description
Fix odoo/enterprise#86141, which was the forward port of odoo/enterprise#86116. As there was no conflict it was forwarded as it, but actually the "+1" query count was not done (the change was considered as useless as it was already in the code, but actually we had to do this +1 query count), making tests still failing.