Daily updates from Odoo
Monday, June 19, 2023
3 changes · master
Enhancements to existing features
The Helpdesk dashboard now opens more useful ticket views by default, making it easier for teams to review recent and closed tickets. Rating information is also clearer when no customer feedback has been received for the day, avoiding misleading zero-percent values.
Original PR description
Improve the following generic UX - avg last 7 days > open the helpdesk.ticket model instead of the helpdesk.ticket.report.analysis one -helpdesk kanban card > tickets closed link > display the list view by default - helpdesk dashboard > my performance > today > average rating > display / % instead of 0.00% if the user hasn't received any rating on today's date task-3251718
The Planning app now reduces unnecessary clicks on material resources when their detail view would not add useful information. When a material resource is archived, its future scheduled shifts are automatically converted to open shifts, helping planners avoid relying on resources that are no longer available.
Original PR description
- we restrict clicking on material resources as the resource's form view does not offer important information. - when a material resource is archived, we transform all of its future shifts into open shifts to be consistent with the behavior we have for human resources. task-3277195
Odoo Studio now lets users choose the currency used by monetary fields directly, and can automatically create or reuse a currency field when needed. This makes monetary fields easier to configure and keeps currency rounding and display consistent across views.
Original PR description
This commit improve the monetary field by changing the way currencies are handled: - The user can now change the currency in the monetary field. - Now creating a new monetary without currencies in…
This commit improve the monetary field by changing the way currencies are handled: - The user can now change the currency in the monetary field. - Now creating a new monetary without currencies in the model also cause the creation of a new currency in the model and the view. Before, the user was asked to create the currency field first. - Now creating a new monetary with a model containing currencies cause the usage of one of the currencies found. Before, the currency were not detected if it's name were not `x_currency_id` or `currency_id`. The currency is also now added to the view if it is not present. The currency choice is saved in the monetary field in the backend side. Meaning that we do not use the `currency_field` attribute in the arch: - To have a better consistency for rounding: if `currency_field` is set to a 3 decimal rounding in the arch and 2 decimal rounding in backend then the backend has the final word as he save in the database by rounding with 2 decimal. - To have a better consistency between views: the same monetary in different views will share the same currency. task-id: 3259535