Daily updates from Odoo
Friday, April 30, 2021
4 changes · master
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