Tuesday, December 19, 2023
3 changes · master
Enhancements to existing features
Users' preferred time scale in calendar-like views is now saved per business record type, so returning to views such as Gantt, Grid, Cohort, or Calendar restores their last selected scale. This reduces repeated adjustments and makes planning views feel more consistent across navigation.
Original PR description
After this commit, the scale for temporal views (gantt, grid, cohort and calendar) is saved in localstorage (resModel dependent) when the user changes the scale value. So when we come back on one of…
After this commit, the scale for temporal views (gantt, grid, cohort and calendar) is saved in localstorage (resModel dependent) when the user changes the scale value. So when we come back on one of this views, the localstorage scale is set as default scale value instead of scale attribute. If no localstorage value exists, then the scale attribute of the component is taken into account. e.g. => I go to the gantt view for project.tasks for the first time => No localstorage exists => default scale = mode arch attribute = week => I don't change the scale => I change view to list => I come back on gantt view => No localstorage exists => default scale = mode arch attribute = week => I change the scale to "year" value => localstorage is updated ! (gantt-scale-of-project.tasks, "year") => I change view to list => I come back on gantt view => localstorage value exists ! => default scale = localstorage value = year PR ENT : https://github.com/odoo/enterprise/pull/53047
Indian accounting now includes default cash rounding using the Half-Up method, helping totals align with common cash payment practices. The chart of accounts has also been updated with income and expense accounts for rounding adjustments, improving consistency in financial records.
Original PR description
Implement default Cash Rounding with Half-Up method for Indian localization. Update Chart of Accounts for Expense & Income with appropriate adjustments. Task Id: 3631283
Timesheet period totals now show clear color indicators when grouped by employee, making it easier to see whether recorded hours are missing, exact, or above expected hours. This helps managers quickly identify employees who may need follow-up, especially for non-standard work schedules.
Original PR description
Before this commit: Currently, we have a color code for the daily total of timesheets encoded per employee, but that doesn't apply to the total number for the period. The daily color code can be misleading because the employee may be missing hours on one day, but that is balanced out with overtime on another day and ultimately has encoded the required number of hours according to their contract for the week/month. The color code for the totals would help users identify at a glance employees who are missing hours - especially when employees are not working standard 40h/week. After this commit: The following color for the totals were applied when grouping by employee: - orange if overtime - green if exact hours - red if missing hours task-3632025