Daily updates from Odoo
Friday, July 26, 2019
11 changes
Resolved issues and error corrections
This update fixes several inventory issues, including showing the correct single-product stock history, avoiding errors when creating stock quantities, and grouping inventory valuation by product. It also improves warehouse form layout and settings visibility, and removes an uninstall error from a related sales timesheet purchasing module.
Original PR description
Related to task #2039731. See commit messages for more details.
This fix adds the employee color setting where it was missing so employee labels and kanban cards can display correctly. It helps keep HR views visually consistent and prevents display issues in tag-style fields.
Original PR description
The color field is necessary to be able to display some fields (many2many_tags) and used in the kanban views -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change prevents users from manually editing inventory loss quantities, avoiding confusing or risky stock adjustments. It also improves quantity editing in special cases and cleans up the inventory list view by hiding unnecessary lot information when it is not relevant.
Original PR description
Fix some issues with quant in master... So, these fixes are for: - Forbid the edition of quant for inventory adjustment; - Enable the multi edit on editable quant list; - Enable edition of quant with no `company_id`; - Minor fix in readonly quant list view to hide `lot_id` when the field is useless. See commit's messages for more details. Task #2035465
This fix prevents an asset from being manually assigned to a different company than its asset category. It helps keep depreciation entries and related accounting records consistent, reducing the risk of cross-company accounting errors.
Original PR description
It was possible to change manually the company of an asset, although its category would be belonging to another company and thus its depreciation lines and journal items also. To tackle this problem, we set the company_id field of an asset as related to its category --- This was already fixed in https://github.com/odoo/odoo/commit/0c76bd3c6373de7bc89818f86d377eb61a74faba, but as it was done in stable (v11) it was reverted by https://github.com/odoo/odoo/commit/8ee2a0d1912e26dbd798acc0194581cca7a998f3 and the forward-port to `master` didn't work. Also, this time, I didn't delete the default. @qdp-odoo -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Customers now see a confirmation message whenever a promo code is successfully applied, even if they did not open the promo code section first. This makes checkout feedback clearer and reduces confusion about whether a discount was accepted.
Original PR description
**Task:** https://www.odoo.com/web#id=2027008&action=327&model=project.task&view_type=form&menu_id=4720 **Pad:** https://pad.odoo.com/p/r.7da68f71d74d6799f4c128fe332075f7 **Description of the issue/feature this PR addresses:** -Previously, success message for promocode was visible only when user clicked on "I have a promocode". even when it was successfully applied. -After this commit, message will always appear once a promocode has been successfully applied. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents the search panel from crashing when a category’s parent information is missing. Users get a more stable filtering experience in views that use category trees.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: category.values[value.parentId] can be undefiend and this leads to a client error Desired behavior after PR is merged: An additional check protects against a client error -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures animated GIFs attached to project task cards continue to animate instead of being treated like static images. It improves the visual display of shared media in the Project kanban view without changing user workflows.
Original PR description
Description of the issue/feature this PR addresses: - Task - https://www.odoo.com/web?#id=1986422&action=327&model=project.task&view_type=form&menu_id=4720 - Pad - https://pad.odoo.com/p/r.96d744296d09b7f0f1a3f826a88bc806 Current behavior before PR: - GIFs were not played. Desired behavior after PR is merged: - GIFs will be played. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Submitting a CRM lead mining request with insufficient credits now shows a clear user-facing error instead of a technical traceback. This helps sales users understand the issue and take action without needing technical support.
Original PR description
Task : https://www.odoo.com/web#id=2032126&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.2b7dbf9ef10079b6e23f8702ef2ed6d3 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes certain appraisal-related employee fields available in the employee profile where they are needed. It avoids unintended access restrictions caused by inherited field settings, improving usability for HR workflows without changing business processes.
Original PR description
In order to be able to use some fields in the employee profile view, we need to remove the groups on the fields, the problem being that related fields always copy the groups of the fields they depend on. This is why those related fields are converted into compute fields
Users can now open details from Actual Demand values in the Mass Production Schedule without encountering an error. This prevents interruptions when planners review demand and replenishment information.
Original PR description
How to reproduce: - Manufacturing > Planning > Mass Production Schedule; - In control panel, clicks on Rows then checks Actual Demand; - Then clicks on a actual demand value in the grid > Traceback. Task #2039731
A test for document tags was adjusted so it no longer fails when the test suite is run multiple times. This improves development reliability and helps prevent false alarms in quality checks, without changing the user-facing product.
Original PR description
This commit prevents the inspector tag input test from failing during subsequent runs of the tests due to a jQuery race condition.