Monday, August 18, 2025
12 changes · master
Resolved issues and error corrections
The Belgian payroll departure wizards now limit employee selection to the company the user is currently logged into. This prevents users from accidentally selecting employees from other companies and helps keep payroll departure processing accurate in multi-company setups.
Original PR description
Added a domain to employees to limit the employee field in the departurre wizard to the logged in company **Steps to reproduce:** - Log into a Blgian Company - Access the Departure wizard through Payroll/Reporting or through the cog actions in an employee. **Issue:** Previously, when using the departure wizard, the employees shown were all the employees across different companies, when in reality it should be employees of the logged in company only **Fix:** Added employee domain so that it allows employees from the current logged in company only Task: 4965719 Forward-Port-Of: odoo/enterprise#92224 Forward-Port-Of: odoo/enterprise#90813
An automated Web Studio test was updated to avoid occasional false failures caused by inconsistent browser event behavior. This helps keep development validation stable without changing the product experience for users.
Original PR description
There was an undeterminism in a test relying on the event beforeunload beign defaultPrevented. For some reason it failed sometimes, probably because of an override somewhere. This commit fixes the problem by asserting other things in the test, arguably even more relevant than before. runbot-error-229754 Forward-Port-Of: odoo/enterprise#92380
This update adjusts the Planning app's automated split-shift walkthrough so it follows the correct path during testing. This helps ensure the related scheduling workflow remains reliable and reduces the risk of unnoticed issues reaching users.
Original PR description
In this commit, we add steps to ensure the tour take the good way.
A failing automated test in the Saudi payroll module was resolved by assigning the correct HR user access group to an employee field. This helps keep payroll functionality stable and ensures employee information follows the expected access rules.
Original PR description
Issue: - The test case test_employee_fields_groups was failing Reason: - The group on the field was not defined. Fix: - added the group hr.group_hr_user on the field. runbot error: https://runbot.odoo.com/odoo/runbot.build.error/230911
The wording for the project documents folder setting was corrected so it no longer promises that task documents are automatically moved into that folder. This helps users understand the current behavior after document access and organization changes.
Original PR description
Before this commit, the tooltip displayed for `documents_folder_id` defined in `project.project` model, said all documents linked to a task of a project will be automatically added inside that folder but it is no longer the case since the refactoring of Documents to simplify the implementation but also let the documents user sorts his documents as he wants since now the access rights are defined by folder. This commit updates the tooltip accordingly. PR simplifying the bridge between documents and project apps: #75214 opw-5000224 Forward-Port-Of: odoo/enterprise#92189 Forward-Port-Of: odoo/enterprise#92164
Payslips now show the correct weekly hours when an employee has a flexible working schedule. This prevents employees and payroll teams from seeing outdated schedule hours on the payslip.
Original PR description
> note: this PR should only be FW'd till `saas~18.4`, after that for `saas~18.5` (i.e., `master`), [this PR](https://github.com/odoo/enterprise/pull/85557) should be merged. ### Steps to reproduce: -…
> note: this PR should only be FW'd till `saas~18.4`, after that for `saas~18.5` (i.e., `master`), [this PR](https://github.com/odoo/enterprise/pull/85557) should be merged. ### Steps to reproduce: - Enable "Flexible Hours" in a working schedule. - Assign the schedule to an employee. - Generate a payslip for the employee. - Observe that the "Working Schedule" section always shows `hours_per_week` from the total hours calculated from the Work Schedule defined before turning on "Flexible Hours" ### Description: - the payslip incorrectly displayed the weekly working hours from the Work Schedule regardless of whether the employee's schedule used flexible hours. ### Cause: - the report template did not check for the `flexible_hours` flag and always rendered the value from `contract_id.hours_per_week`. ### Fix: - added a condition in the payslip template to check if `flexible_hours` is enabled. - if true, it displays `full_time_required_hours` from the working schedule instead of the contract's `hours_per_week`. task: 4719717 Forward-Port-Of: odoo/enterprise#92441 Forward-Port-Of: odoo/enterprise#83910
This update fixes an incorrect provision code in the Swiss payroll configuration. It helps ensure payroll calculations and reporting use the right setup, reducing the risk of payroll processing errors.
Original PR description
Forward-Port-Of: odoo/enterprise#92477
Printer tests from the device form now handle cases where the IoT device does not respond in time. Instead of causing an unclear system error, users receive a proper notification, making troubleshooting smoother.
Original PR description
When testing printers from the device form, if no response was received from the IoT after the websocket timeout, we did not provide any message. This resulted in errors when providing `undefined` to the notification service. Forward-Port-Of: odoo/enterprise#92391
Users can now sign documents directly from the chatter without losing the document reference. This prevents signing actions from failing or opening with missing context, making the workflow more reliable.
Original PR description
Before this fix, when a user signed a document from the chatter, the reference_doc context was not passed correctly. This PR ensures the context is properly set so signing from chatter works as expected.
A timesheet holidays test was updated so it no longer fails depending on the time of day or user timezone. This improves reliability of automated checks without changing customer-facing behavior.
Original PR description
Before this commit, when the `test_timer_methods_handle_project_access_restrictions` test is executed after 22h in UTC the test failed because the timezone of the current user is the belgian one. This commit makes sure the date and timezone no longer affects this test since it is not the purpose of this test. runbot-error-230490 Forward-Port-Of: odoo/enterprise#92264
The Belgian payroll employee form now places the “Seniority at hiring” field under Education instead of Citizenship. This makes the information easier to find in the section where users are more likely to expect it, with no change to payroll calculations or employee data.
Original PR description
Move Seniority at hiring from Citizenship to Education group in employee form. In this PR, we moved seniority at hiring from the Citizenship to the Education group in the employee form. Related task: 4936767. Forward-Port-Of: odoo/enterprise#90137
Peru PLE reports 5.1 and 6.1 now keep the original account move name in the report description instead of removing spaces or slashes. This helps ensure submitted reports retain the full original information, reducing audit-related risk with tax authorities.
Original PR description
Problem: For PLE reports 5.1 and 6.1, the value for `glosa` was being modified (i.e. blank spaces and slashes removed). Although SUNAT accepts the modified value, no information should be removed in the case it might lead to issues with tax authorities during an audit. Solution: The value for `glosa` on the reports should be the exact account move name. opw-4803060 Forward-Port-Of: odoo/enterprise#92271 Forward-Port-Of: odoo/enterprise#91967