Thursday, December 14, 2023
7 changes · master
Resolved issues and error corrections
This change makes an automated business flow test wait for product details to fully update before continuing. It helps prevent false test failures and improves confidence that core product selection workflows remain reliable.
Original PR description
Before this commit, since changes made in odoo/odoo#131680, the step checking the name field correctly contains the name of the product selected in the `data-tooltip` has been replaced by a step checking the same tooltip but on `product_id` or `product_template_id` field because the tooltip data attribute has been removed on text field. Because of that changes, we no longer wait the onchange execution since the tooltip in `product_id` or `product_template_id` field is directly filled in when the user selects the product, compared to the one in the name field which is filled in when the oncahnge rpc is done. This commit adds an extra step to wait the execution of the onchange when it is needed. To do that, the step will check the `product_uom_id` field is correctly set. By doing that, we can be sure the next steps will be correctly executed and will not be altered when the Framework JS will get the result of the onchange to reload its components. runbot-52609
This fixes an issue where loading demo data could create a new country-specific company but leave users working in the original company. After the change, Odoo automatically switches to the newly created company that matches the selected country, helping demo environments reflect the intended setup.
Original PR description
Description of the issue/feature this commit addresses: When initializing a database without demo data then setting a country on the company that is being used. If demo data are loaded, a new company is created with the demo data of the country that was set on the initial company. The issue lies in the fact that once that demo data is done loading, the used company is still the initial one while we would want to use the new one. --- Desired behavior after the commit is merged: Adding this commit, a new operation is done after the demo data is loaded. When demo data are done loading, we switch to the company that uses the country which was set on the initial company before loading the demo data. --- task-3600521 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resume line type names in the Skills app can now be shown in the user's language instead of always appearing in English. This improves localization for employees and HR teams using Odoo in non-English languages.
Original PR description
Without the translate=True, the names of these types cannot be translated so they will always appear in English regardless of the user's language. Because translation of Char fields requires a db change, we only add this fix into master. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Manufacturing users can now mass produce serialized products by pasting a list of serial numbers without being blocked by the separate "First Serial Number" field. This fixes an unnecessary validation issue and makes serial-number assignment smoother during production.
Original PR description
Steps to reproduce: - Create an MO for a product that requires a SN for example 2 units - Click on massproduce - paste your SNs in "Produced serial numbers" Bug: "First SN" field is required Fix: use python constraint to check that either field is filled opw-3634341
Mail notification preference changes are now handled by the server instead of relying on the browser form logic. This prevents errors when creating users or changing notification settings and keeps the preference update consistent across open tabs and affected users.
Original PR description
There is a traceback each time we create a new user or changes related to "notificaiton_type" in the form. The bug is in the 'onRecordSaved', 'this.mailStore?.user.user.id' will problematic because the this.mailStore.user is undefined. The fix is to make the change of notification_preference be sent on the bus from the python instead. So that it works on all tabs and for all users. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an error that could appear when opening the Field Service task Gantt view grouped by assigned users. The view now correctly considers skill-based searches when showing available users, helping dispatchers plan work without interruptions.
Original PR description
Before this commit, when the user goes to the gantt view of task in Field Service, the user got an error because of a wrong usage of the domain in the group expand of user_ids. This commit fixes the issue and also make sure the group_expand of user_ids first take into account the search on skills to add users in the gantt view of tasks when the group by is `user_ids` field. task-3349411
The Planning app no longer crashes when opened in a database without demo data. This ensures users can access scheduling features even when no working interval information is available yet.
Original PR description
Steps to reproduce: ------------------- - install planning without demo data - try to open planning module Issue: ------ When trying to open the planning module, a traceback occurs. Cause: ------ The issue arises when attempting to get a row from workIntervals, even when it is undefined. Solution: --------- Ensure workIntervals is available before attempting to retrieve rows from it.