Daily updates from Odoo
Tuesday, June 21, 2022
8 changes
Enhancements to existing features
Helpdesk emails are easier to read, and field service users can access navigation actions more directly from customer and task records. The field service sales product selection screen also now gives clearer guidance when no products are available.
Original PR description
This commit brings some user experience improvement. In helpdesk: - Add a line break between the content of the email and the 'this customer survey has been sent...' indication in mail template In industry_fsm: - Display the 'navigate to' button in project.task form view In industry_fsm_sale: - Change the nocontent helper message of choose product menu of field service task-2792027
Search panel categories based on selection fields now appear in the intended business order in Gantt views. This makes status lists, such as time off approvals, easier to read and prevents confusing category placement.
Original PR description
Before this commit in search panel category and in list, kanban & gantt views, the order of categories was unpredictable. That can cause some categories not being in correct place, like in timeoff where the order is - To Approve - Approved - Second Approval But should be - To Approve - Second Approval - Approved This commit preserves the order defined for fields that are selection field in Gantt views. Task id: 2317536
VoIP configuration has been updated to rely on each user's settings, making phone-related preferences more consistent across the system. This should improve reliability and maintainability of calling features without changing the overall user workflow.
Original PR description
Part of task-2804807.
Helpdesk teams now handle portal followers more predictably when team visibility changes. Portal followers are only removed when visibility changes away from portal access, and users receive a warning when a visibility change will automatically add or remove followers.
Original PR description
Currently, portal followers of a team and its tickets are removed when the team visibility is changed to something else than portal. => We want to keep the behavior, but only when changing the visibility from portal to something else. When a follower is added to a ticket in a team in a non-portal visibility, all of its portal followers are removed. => We want to remove this behavior, as it is not intuitive This PR implements those changes, and also adds a warning when changing the visibility of the team if that change will automatically add/remove followers to the team and its tickets. Related: https://github.com/odoo/odoo/pull/87747 Task-2812551
When a Helpdesk stage is restored, users are now prompted to restore the archived tickets within that stage as well. This helps keep ticket visibility consistent and prevents teams from accidentally leaving relevant work hidden after reopening a stage.
Original PR description
Currently, all of the tickets contained in a stage are archived when the stage is archived. However, the tickets remained archived when the stage is unarchived. So in this commit, If the user unarchives a stage, ask the user to unarchive the tickets it contains in the process. task-2835624
Spreadsheet autofill now better handles larger number sequences when filling cells. This makes data entry smoother and reduces manual corrections for users working with spreadsheets in Documents.
Users can now widen or narrow the Documents search panel, making long workspace names easier to read. Workspace names also appear on hover, helping users identify folders without guessing or changing their naming conventions.
Original PR description
PURPOSE If you work with long workspace names, they can be hidden by the size of the left menu. In that case, we don't have any option to see the full name. SPECIFICATIONS Allow the user to resize the search panel and Display the name of the workspace on hover Task-2641699
Document uploads now check the maximum allowed file size before starting, so users get a clear warning instead of waiting for a technical server error. Administrators can adjust the limit through system settings, helping businesses match upload rules to their hosting setup.
Original PR description
PURPOSE Currently, when we add a file too large, we wait some times before we are notified by Odoo "413 Request Entity too large" SPECIFICATIONS - Catch correctly the 403 error to display a user friendly message instead of the technical error that doesn't mean something for common humans. But this will be displayed when the upload already started. - Add a ir.config.parameter (System Parameter, see screenshot), unset by default But let's say that the limit on the instance is set to 500MB and if the administrator of the database wants to set the limit to 50MB, it could be possible from the interface, and in that case, it would be possible to display a modal before the upload starts to notify the user that his file is too big. - Set the limit correctly for saas databases, as we are in charge of the hosting (and thus the nginx configuration). LINKS PR #15491 Task-2313367