Monday, May 19, 2025
31 changes
2 changes
Resolved issues and error corrections
This fix ensures project planning correctly identifies overlapping tasks when filters include related information. It helps prevent scheduling conflicts from being missed and improves the reliability of planning calculations and related tests.
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…
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. odoo/odoo#207404
Manufacturing orders no longer automatically mark components or byproducts as picked just because the production quantity is changed. This keeps inventory consumption and byproduct production aligned with explicit user actions or final production completion, reducing unintended stock updates.
Original PR description
When the quantity being produced in a MO is updated, the consumption of components and the production of byproducts were automatically picked. However, this behavior should only occur when the user manually picks it or when the production is completed. This commit fixes the issue and updates some tests to reflect the intended behavior. task: 4314900
4 changes
Resolved issues and error corrections
Rental order reports now add clearer spacing between invoicing and shipping addresses. This makes printed or shared reports easier to read when both addresses are shown.
Original PR description
Follow the changes made in community commit. When a Shipping Address is displayed inside the `information_block` there is no spacing to differentiate it from the Invoicing Address, making it harder to read. Note: there are leftovers `:` characters that will be removed on master forwardport to avoid wiping existing translation on stable (not worth) task-4730464 Community PR: https://github.com/odoo/odoo/pull/207725
The loan accounting app now handles missing demo data more safely during installation. This prevents an installation crash in cases where accounting demo data is present but loan demo data cannot be loaded, improving setup reliability.
Original PR description
Prior to this change, if the demo data were loaded for account but couldn't be for account_loans, its installation would simply crash trying to reference an unknown xml_id 'account_loans_loan_demo1'. opw-4790398 upg-2793930
This fixes an automated field service test that could fail when customer search suggestions loaded too slowly or in the wrong order. The change helps keep validation runs reliable, reducing false failures during quality checks without changing normal user behavior.
Original PR description
The tours fails because when we edit the value in the input field of customer it clicks on the field and then fills out the value and then a change event is propagated and text based autocomplete results are shown (and m2o fields with partner autocomplete wizard are a tad bit slower), after that tours moves to next step and the new result dropdown menu is not loaded and it gets its reference from older menu which got closed in between and tries click it and no change is reflected but the new menu is not closed and tour continues to industry_fsm_report where we create a worksheet from a many2one field using create and edit so we click on the m2o input and wait for options but as partner field loaded dropdown is loaded it clicks on click and edit trying to create a new partner and opening thus fails the tour. Fix: - After entering the text to instantly load the dropdown by clicking on it and give time for loading of menu. task-4800194
The web_studio report editor now keeps the user's cursor near their last edit after saving and reloading XML content. This avoids sending users back to the top of the editor, making repeated edits less disruptive.
Original PR description
…ve and reload sources In the reportEditor edit the xml, modify a view's arch and save. Before this commit, the cursor position in the XMLEditor was reset to [0,0]. After this commit, we restore the position of the cursor according to the start position of the last edition. opw-4745895