Daily updates from Odoo
Navigate
Branch
Friday, April 30, 2021
10 changes
Enhancements to existing features
Planning users can now filter schedules by job title and quickly identify shifts that conflict with other commitments. The update also improves reliability by fixing an allocation calculation issue and correcting how planned hours are displayed in schedule popovers.
Original PR description
This PR aims to add filters on job title and shifts in conflict to planning and project_forecast. === Filters We implement for slot in conflict a search method for a simple reason : the creation or edition of an other slot may affect the value of those computed fields. To take account of those environnement changes, we have to define _search methods. task-2215216
Belgian payroll DmfA declarations were updated to handle official location codes correctly and make testing/export setup easier. This reduces errors caused by long ONSS codes and removes fields that are no longer needed.
Original PR description
It is not redundant with the new hr.work.location model. Another issue was that the code is an integer field. Unfortunately, the ONSS code the is a 10 digits-long string, and the number was sometimes above MAXINT. TaskID: 2501299
The tax report carryover workflow has been made easier to find and use, with cleaner screens and interactions. This helps accounting users manage carryover amounts more confidently and reduces the chance that important reporting actions are overlooked.
Original PR description
Implements various small improvements in order to make the carryover functionality a bit less hidden, with a cleaner UX. Task id #2500684
Resolved issues and error corrections
Failure notifications now update immediately for all relevant channel members, not just the original message author. This prevents users from thinking nothing happened when someone else resolves a delivery failure, removing the need to refresh the page.
Original PR description
**Current behavior before PR:** Currently, failure notifications are sent to the author of the message that the failure is concerning. However, if another user than the author is resolving the failure, he is not receiving any notification without refresh the page, so it appears as if nothing happened even though the failure was indeed resolved (either message resent, or failure ignored). **Desired behavior after PR is merged:** Failure notifications will also be sent to the members of the channel instantly that the failure is concerning and also update the status of failure notification instantly, no refresh needed to show the updated status. **LINKS:** Task-2178257
Code cleanup and technical improvements
This change moves shared image and font files into a cleaner folder structure across several Odoo Enterprise apps. It should not change day-to-day functionality, but it helps keep the codebase easier to maintain and align with the related Community update.
Original PR description
Community: https://github.com/odoo/odoo/pull/69614
Miscellaneous changes
Forward-Port-Of: odoo/enterprise#17876
Original PR description
Forward-Port-Of: odoo/enterprise#17876
The changed test uses the drag&drop helper, and an operation does not work as expected with the given params on chrome 90. The runbot currently uses chrome 80, so it is not an issue, but if your chrome is up-to-date, and you try to run the test suite, this test would fail. Here, we want to drop a text span after another text span, i.e. on its right. Before this commit, it was dropped on its exact center, which appearently was considered as 'after' before chrome 90, but 'before' as of c
Original PR description
The changed test uses the drag&drop helper, and an operation does not work as expected with the given params on chrome 90. The runbot currently uses chrome 80, so it is not an issue, but if your chrome is up-to-date, and you try to run the test suite, this test would fail. Here, we want to drop a text span after another text span, i.e. on its right. Before this commit, it was dropped on its exact center, which appearently was considered as 'after' before chrome 90, but 'before' as of chrome 90. Specifying explicitely that we want to drop it after is harmless and makes the test more robust. Forward-Port-Of: odoo/enterprise#18033
PURPOSE Currently the "Pivot properties" menu item only appears if the formula starts with =PIVOT(... With this fix formulas like =-PIVOT(...), =3*PIVOT(...)+2 also allow to display the pivot properties of the cell. task-id: 2294260 Forward-Port-Of: odoo/enterprise#17945 Forward-Port-Of: odoo/enterprise#13763
Original PR description
PURPOSE Currently the "Pivot properties" menu item only appears if the formula starts with =PIVOT(... With this fix formulas like =-PIVOT(...), =3*PIVOT(...)+2 also allow to display the pivot properties of the cell. task-id: 2294260 Forward-Port-Of: odoo/enterprise#17945 Forward-Port-Of: odoo/enterprise#13763
Steps: - Install Contacts and Data Cleaning - Go to Contacts - Create two contacts with the same names - Go to Data Cleaning / Configuration / Rules / Deduplication - Create a new rule: - Model: Contact - Duplicate Removal: Archive - Deduplicate - Merge the two same contacts - Go to Contacts Bug: One of the two contacts has been deleted instead of archived. Explanation: Models can implement their own merge method by defining `_merge_method()`. It is the case with Contact a
Original PR description
Steps: - Install Contacts and Data Cleaning - Go to Contacts - Create two contacts with the same names - Go to Data Cleaning / Configuration / Rules / Deduplication - Create a new rule: - Model: Contact - Duplicate Removal: Archive - Deduplicate - Merge the two same contacts - Go to Contacts Bug: One of the two contacts has been deleted instead of archived. Explanation: Models can implement their own merge method by defining `_merge_method()`. It is the case with Contact and its merge method only deletes duplicated contacts. This commit shows the user when the merge method is model specific and doesn't offer them to chose between archiving and deleting anymore if it's the case. opw:2491292 Forward-Port-Of: odoo/enterprise#17719
Forward-Port-Of: odoo/enterprise#18040 Forward-Port-Of: odoo/enterprise#18021
Original PR description
Forward-Port-Of: odoo/enterprise#18040 Forward-Port-Of: odoo/enterprise#18021