Tuesday, May 21, 2024
7 changes · master
Enhancements to existing features
The timesheet validation menu now uses one “Last Period” option instead of separate last week and last month choices. This makes the view follow each user’s saved grid time scale, reducing confusion and keeping validation screens aligned with their preferences.
Original PR description
## [IMP] timesheet_grid: merge To Validate menus in only one Before this commit, since the merge of https://github.com/odoo/enterprise/pull/53047, the current scale chose by the user is now stored…
## [IMP] timesheet_grid: merge To Validate menus in only one Before this commit, since the merge of https://github.com/odoo/enterprise/pull/53047, the current scale chose by the user is now stored into the local storage, it means the `To Validate > Last Week` and `To Validate > Last Month` can be merged into one menu to display the `Last Period` and we will use the scale stored into the local storage instead of forcing the scale in a menu. This commit replaces `To Validate > Last week` and `To Validate > Last Month` by `To Validate > Last Period` to take into account the scale stored in the local storage and go back to the previous period. ## [IMP] web_grid,timesheet_grid: remove grid_range in context and dead code Before this commit, since the local storage now store the range, it is no longer needed to force to use another range by using `grid_range` inside the context, this context was essentially used for the `To Validate > Last Week` and `To Validate > Last Month` menus but those menus will be replaced by `To Validate > Last Period`. This commit removes the dead code because the group expand employee is made in the JS code by doing an additional rpc inside the grid view for `All timesheets` menu. This commit also removes the `grid_range` in the context and the using of that context since it is no longer needed. ## [FIX] web_grid: use the right range to use in the grid view task-3893907
Project task scheduling in Gantt views now handles dependencies more predictably, moving only the tasks that truly need replanning and avoiding newly created conflicts. Planning also better respects working calendars, multi-user assignments, and dependencies across different projects, helping teams keep schedules realistic and easier to manage.
Users can now open employee cards directly from member lists in channels, live chat channels, and groups, making it easier to view colleague details in context. Employee cards also show work location with an icon when available, improving visibility of where people work.
Original PR description
[Mail] 1. Open card from members list for channels, livechat channels, groups; [Employees] 1. Add work location + corresponding icon after the phone number, if specified; 2. Linting changes; https://github.com/odoo/odoo/pull/157980 task-3710112
Shop floor users now get clearer play and pause controls on work orders, instead of relying on the whole header area. Quality checks can be collapsed or expanded, and users can quickly move to the next operation, making production workflows faster and easier to follow.
Original PR description
Task: 3848751
Rental orders now automatically create a planning shift when confirmed, covering the selected rental period. This reduces manual scheduling work and helps teams align rentals with staff or resource planning more reliably.
Original PR description
In this commit, the planning feature has been integrated with the rental process. When a user confirms an order, an automatic shift is now generated for the selected rental period. Task: 3468698
Financial reports that use a simple horizontal grouping now show a total column when comparison growth is not enabled. This makes it easier for users to quickly see overall totals without manually adding grouped values together.
Original PR description
This commit will improve the Ux of horizontal group by adding a total column on the report depending on those conditions: - Growth comparison is not activated - Only one columns - Only one level of group by task-3881278
Leaving large spreadsheet documents is now faster because the system no longer exports the full spreadsheet data during exit. It now checks the spreadsheet structure directly when needed, reducing delays for users working with large files.
Original PR description
Currently, when leaving a spreadsheet document, the data is exported and given to a callback. Exporting the data can take several seconds on large spreadsheets though. It slows the user experience. Currently, this exported data is only used for Documents to check if the spreadsheet has multiple sheets. We don't need to export the full data, we can just read the spreadsheet model. Task: 3934885