Tuesday, April 25, 2023
7 changes
Enhancements to existing features
Odoo Studio now lets users choose a default grouping for list views directly from the list view editor sidebar. This makes it easier to configure how records are organized for end users, while clearly indicating that the grouping will apply outside the Studio editing preview.
Original PR description
This commit adds a "Default Group By" field in the list view editor sidebar, allowing the user to edit the default group by. The group by is not applied inside of the studio view so the user can keep editing it. When a default goup by field is selected, a message informs the user that the changes are applied even though they are not visible. Task ID: 3259513
The helpdesk portal now shows the newest tickets first when customers sort by reference, helping them find recent requests faster. Customers also receive a clear confirmation when they close a ticket, reducing uncertainty and improving the support experience.
Original PR description
This PR brings the two following improvements to the helpdesk portal: - When sorting tickets by reference, sort in decreasing order instead of increasing. - Display a notification when a customer closes a ticket through the portal. Task-3186588
Payslip periods now automatically adjust to the employee’s payroll structure and pay schedule instead of defaulting to one month. This helps payroll teams create payslips with the correct duration and adds a warning when a payslip period does not match the expected schedule.
Original PR description
Before this commit, creating a payslip would always compute the duration of it on one month, even though the pay schedule defined in the payroll structure says otherwise. After the commit, setting the employee for the payslip will adapt the dates accordingly so that the duration is correct. This commit also adds a warning message if the payslip duration isn't the right one. task-2977799
Companies that belong to the same VAT unit will now get fiscal positions set up automatically so they do not charge VAT to each other. This helps keep intercompany invoicing aligned with VAT unit rules and reduces manual configuration work.
Original PR description
Companies in a VAT unit shouldn't charge VAT to other companies in the same unit. This commit creates new fiscal positions for each company in the VAT unit, and applies it to the related partners. Task-2584180
Shipping carrier integrations now send each product's HS code when goods are shipped internationally. This helps customs identify products correctly, reducing the risk of delays or rejected shipments for cross-border deliveries.
Original PR description
Task :- https://www.odoo.com/web#id=1831519&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 PAD:- https://pad.odoo.com/p/r.5437371fcde0a83ba86d994c6eb4c7ca
Timesheet users can now see and manage the running timer directly from list and kanban views, not only from the grid view. This makes time tracking more visible and easier to access while working across different timesheet layouts.
Original PR description
*:timesheet_grid related: https://github.com/odoo/odoo/pull/105362 task-2276491
Users now receive a confirmation dialog when changing or moving a knowledge article that is used by a Helpdesk team. This prevents surprise errors and clearly explains that continuing will remove the article from the affected team’s help page.
Original PR description
*: website_helpdesk_knowledge: Say an Knowledge Article A set on a Helpdesk Team T as T.website_article_id. Prior to this commit, when changing A.website_published or setting A.parent_id, we used to raise a ValidationError. Now, we open a Confirmation Dialog informing the user that A is set on T, and that, if he wants to continue, T.website_article_id will be unset. Note : This code is not optimal performance wise : we add a RPC call both before and after the Dialog. `KnowledgeArticle.get_helpdesk_teams()` could have been replaced by a computed field `helpdesk_team_ids` and added to the view. However, say we are on article A and want to move B ; as we are in form view, we don't have B's data. It might be possible to force it, but it would add too much complexity. task-2984032