Thursday, November 16, 2023
5 changes
3 changes
Enhancements to existing features
Field Service task analysis reports now present time-based measures in an easier-to-read hours-and-minutes format and hide zero values that can clutter reporting. Default pivot and graph views are also better grouped, helping managers spot trends by month and project more quickly.
Original PR description
This PR makes the following improvements: ->Remove 'remaining hours percentage' measure from task analysis. -> change 'total hours' into 'total hours spent' and 'working days to assign' into 'Working…
This PR makes the following improvements:
->Remove 'remaining hours percentage' measure from task analysis. -> change 'total hours' into 'total hours spent' and 'working days to assign' into 'Working Days to Assign'.
->In pivot view and graph view of task analysis report, following measure will be appear as hh:mm.
-overtime, total hours, working hours to close, working hours to assign
->Hide the value if it is equal to 0 for the following measures:
-hours spent, overtime, progress, total hours, working hours to assign,
working days to assign, working hours to close, working days to close ->When calculating the average the following measures should exclude records with a value of 0
-progress, working hours to assign, working days to assign,
working hours to close, working days to close.
->Set the by default grouping for the following task analysis report
-for pivot view add the group by 'create date>month' and made changes
following changes in measure :
-count, working hours to assign, working hours to close, total hours
-for graph view add the group by 'create date>month>project'.
task-3514437Helpdesk teams can now access chatbot configuration directly from the live chat settings, making it easier to set up automated support flows. The live chat ticket search command now shows results in smaller batches with a load more option, helping agents browse matching tickets without being overwhelmed.
Original PR description
List of features this PR implements: - add a 'chatbots' menu under the 'configuration > tags' menu item / add a '-> configure chatbots' link that should redirect users to the configuration > chatbots…
List of features this PR implements: - add a 'chatbots' menu under the 'configuration > tags' menu item / add a '-> configure chatbots' link that should redirect users to the configuration > chatbots menu - /search_tickets command: if there are more than 5 results, display a 'load more' button ### Implementation details For the search_tickets command: This command triggers the method _execute_command_helpdesk_search_, it now calls a new method _fetch_ticket_by_keyword_ that return the msg containing links to the tickets corresponding to the query, by default the fetch tickets return only 5 tickets, if there are more than 5 ticket corresponding to the query a link *load more* will be added to the messages. When clicked this link will rpc call _fetch_ticket_by_keyword_ to fetch 5 more tickets this time, the steps can be repeated until all the tickets are fetched. To know if there are more tickets corresponding to the query than returned, we try and fetch one more ticket than the limit (so if we're at 5 we try to fetch 6 tickets), the last ticket will be removed from the list and the load more link will be added to the message The ticket fetching is ordered by 'id desc', fetching first the *6* tickets with the highest id corresponding to the query. The sixth tickets is ditched but it's ID is saved in the button tags so it can be recovered in the frontend to be given back to the backend in case the user clicks on load more. Once clicked the backend will only fetch ticket with ID lower or equal to the last ticket ID. Community PR: https://github.com/odoo/odoo/pull/131702 Task-3186593 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When a helpdesk ticket is created with people copied on the email, those contacts are now automatically added as followers. This helps copied stakeholders receive updates and stay informed as the ticket progresses.
Original PR description
This commit's purpose is to ensure that when a ticket is created with an email_cc field set, the partners linked to this email will be set as follower of the ticket, in order for them to be able to follow the ticket evolution task-3251657
2 changes
Enhancements to existing features
This update changes the icons used for pivot and list menu items in the spreadsheet editor to match Odoo's standard icons. The change also consolidates duplicate pivot and list insert menu items, improving the user interface consistency and reducing menu clutter.
Original PR description
This commit changes the icons of the pivot/list menu items to match the standard pivot/list icons of Odoo. Task: [3559271](https://www.odoo.com/web#id=3559271&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
Portal pages like tickets and tasks were loading slowly because they were downloading oversized avatar images. This fix reduces the avatar file size from the largest version to a smaller one that still looks perfect on screen, significantly improving page load times especially for users with slower connections.
Original PR description
## Description Portal routes `/my/tickets` or `/my/tasks` were reported slow to load with many items. ## Analysis The avatars that are loaded are of too large sizes (encoded in base64) compared to their rendering size. `o_avatar` limits the dimensions to `1.7145em` (roughly `27px` on desktop), so it's useless to load `avatar_1024` for those image sources. This has a significant impact when the user has a slow connection, the server is hosted far away from the user, or the images used are of badly compressed (so each images takes a quite a few MiB). ## Fix Scan for all instances of the usage of `avatar_1024` on an `<img>` with the class `o_avatar` and reduce it to `avatar_128`. ## Reference opw-3470171 ## Linked PR https://github.com/odoo/odoo/pull/141877 Forward-Port-Of: odoo/enterprise#50557