Daily updates from Odoo
Tuesday, July 22, 2025
4 changes · master
Resolved issues and error corrections
Fixed an issue that could prevent project task overlap checks from correctly handling filters based on related task information. This helps ensure planning conflicts are detected accurately and reduces the risk of missed scheduling issues.
Original PR description
The query that determines overlapping tasks is making two different Query objects: the first one for the main task and the second one for overlapping tasks. The second query is joined into the first one, injecting the second one's where clause as join condition, but that composition does not work if the second query has extra joins. Those extra joins come from related fields that may occur from the domain. The fix consists in recomposing the query with a join condition that does not depend on a dynamic domain, and injecting the domain in the where clause of the main query. With this strategy, the joins that appear because of the related fields in the domain are part of the main query, and are no longer lost by the composition. Note also that the test test_same_user_overlap_with_allocated_hours_less_than_workable_hours was actually broken, because the field allocated_hours wasn't flushed when doing the SQL query. The new query flushes the field, and the test has been fixed.
This fix makes Odoo more stable when working with newly created records before they are saved. It prevents errors during automatic field updates and display-name calculations, reducing interruptions in workflows such as field service reporting and Belgian tax reporting.
This change fixes an access problem that could prevent users from using the salary configurator correctly. It removes an unnecessary company-related recalculation that was causing permissions issues, while keeping company filtering already handled elsewhere.
Original PR description
Since this commit: https://github.com/odoo/enterprise/commit/b68569868c00765bca910b5630a72db75347c03d, the salary configurator had an access issue on hr.job model. This is due to the compute method on company_id introduced in the previous commit. As the properties definition field of the hr_job is defined on the company, it was recomputed every time the company commute is triggered. Additionnaly, this compute on the company_id is useless as the domain on the contract_template_id is already filetered based on the company. A test for this is added in this PR: https://github.com/odoo/enterprise/pull/90412 task-4951648
When a report is opened in Studio without an existing template, the system now automatically creates the standard views it needs. This prevents crashes and lets users continue editing reports created from the technical menu.