Thursday, April 4, 2024
2 changes · saas-17.1
Resolved issues and error corrections
This fix prevents entire list rows from appearing highlighted as errors when only one field has an invalid value. Users can now more easily identify the specific cell that needs correction, reducing confusion during data entry.
Original PR description
In [this commit](https://github.com/odoo/odoo/commit/a010a22f3ae6dda8c45cb6a4c36bb38f949b33e9) we introduced a new behavior on our fields having an invalid state applying a slight danger background.…
In [this commit](https://github.com/odoo/odoo/commit/a010a22f3ae6dda8c45cb6a4c36bb38f949b33e9) we introduced a new behavior on our fields having an invalid state applying a slight danger background. However in the list view table, the background of the inputs that are at the same line were displaying the error state. -> To reproduce, enter a wrong value in the list view, save and click outside of focus. This commit resets the `o-input-background-color` to it's initial value inside the list view making it fallback to transparent, not displaying the bg when line is in error state and avoiding overlapping with the background already set on the td. task-3644895 | Before | |:------:| |  | | After | | | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a warning message appearing when users share projects with tasks created using the 'blockby' feature. The issue stemmed from a technical error in how Odoo processed temporary project records, leading to incorrect data comparisons. This change ensures warnings are suppressed when sharing projects, improving user experience.
Original PR description
Steps: - Install project app. - Share a project which contains a task with blockby task. - Open that project in project sharing and keep login via admin. - Edit something in blockby page. Issue: - Warning displaying about other private project task blockby even though there are no task in blockby which from other project. Cause: - Computation on changing project task block by tree call compute of depend_on_count field but since record is just temparory save it get _origin instead of actual record and because of origin it fails to get actual id key data from dictonary. Fix: - Get id from origin if record is _origin record to properly get and set data. task-3764782