Tuesday, December 31, 2024
4 changes · 18.0
Resolved issues and error corrections
This fix prevents an error when creating a manufacturing order component if the unit of measure is removed and the quantity is changed. Users can now adjust the quantity without the screen crashing, improving reliability during manufacturing order entry.
Original PR description
Currently, a traceback is occurring when the user removes the `uom` and tries to change the `product_uom_qty` in the stock move. While creating the Manufacturing Order. To reproduce this issue: 1) Install MRP and enable UOM from the configuration 2) Create a new mrp order and add a product in components 3) Remove the UOM and change the `To Consume` value Error:- ``` AssertionError: precision_rounding must be positive, got 0.0 ``` This traceback occurs because when the user changes the `product_uom_qty`, an onchange method `_onchange_product_uom_qty` will triggered. In that method, `float_round` is used with precision_rounding getting from `product_uom.rounding`. It leads to the above traceback as `product_uom` has an empty recordset. sentry-6170644216
When creating a recruitment application, key contact fields such as email, phone number, and LinkedIn profile now appear immediately. This makes it easier for recruiters to enter applicant details without first assigning a candidate.
Original PR description
Steps to Reproduce: • Install the Recruitment app. • Open any Job Position. • Click New to create a new application, The Email, Phone Number, and LinkedIn Profile fields are not visible until a candidate is assigned. Cause: The fields were set to be conditionally invisible based on candidate assignment. Fix: Removed the visibility conditions to ensure these fields are always visible. task-4385022 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
POS receipts for GCC countries now show the cashier name only once instead of repeating the "Served by" text. This improves receipt clarity for customers and staff while leaving receipts in other countries unchanged.
Original PR description
Description of the issue/feature this PR addresses: In GCC countries, the POS receipt displays duplicate "Served by" text due to inconsistent handling of the cashier field in the getReceiptHeaderData method. Current behavior before PR: 1. The "Served by" text is duplicated on POS receipts for GCC countries. 2. The issue arises from both the base implementation and the l10n_gcc_pos module adding the "Served by" prefix. Desired behavior after PR is merged: 1. The POS receipt correctly displays the cashier's name without duplication. 2. For GCC countries, the "Served by" prefix is removed, and only the cashier's name is displayed. 3. Non-GCC countries remain unaffected. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Several automated walkthroughs were made more precise and reliable across sales, e-signature, helpdesk forum, and subscription flows. This helps reduce false test failures and supports smoother validation of important customer-facing processes.
Original PR description
In this commit, we fix 4 tours by being more precise on the triggers and/or adding intermediate steps to ensure the proper conduct of the tour. We take advantage of this commit to linter the tour files.