Tuesday, July 28, 2020
4 changes · master
Enhancements to existing features
Outdated reporting filter settings were replaced with their current equivalents in Recruitment and Point of Sale. This helps keep reports consistent with the modern system behavior and reduces maintenance risk without changing day-to-day workflows.
Original PR description
…t_measures and pivot_column_groupby. Task: https://www.odoo.com/web#id=33834&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Adds a new display option so time values can omit unnecessary zero minutes, showing values like 1 instead of 1:00. This improves readability for grid totals and similar views where compact time summaries are easier for users to scan.
Original PR description
This commit adds noZeroMinuteHour option to formatFloatTime. The noZeroMinuteHour option can be used to format the value like 1 instead of 1:30 This format behavior is wanted for fields in the web_grid module. task - 2261846
Analytic fields on posted accounting entries are now read-only because changing them after posting has no practical effect. This reduces confusion for users and helps keep posted financial records clearer and more consistent.
Original PR description
Analytics fields are currently updatable when the move has been posted, even though editing them as no effect. This change make them read-only when the move has been posted. Task ID: #2299319 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Several Odoo business apps were updated to replace outdated internal definitions for reports and window actions. This keeps payroll, accounting, rental, manufacturing, point of sale, and localization features compatible with newer platform standards without changing day-to-day workflows.
Original PR description
Cf odoo/odoo#54564 Task 2296297 Note: instances of `attachment_use="False"` were replaced by `<field name="attachment_use">True</field>`: `<report>` never evaluated that value, so specifying the attribute would always opt into attachment_use, unless the value was set to empty (at which point you might as well leave the attribute out).