Odoo Changelog — 2024-04-10

Wednesday, April 10, 2024

4 changes · master

Bug Fixes(4)

Resolved issues and error corrections

[FIX] l10n_au_hr_payroll: Fixes groups on hr.employee

Enterprisemasterl10n_au_hr_payroll

This fixes access settings for Australian payroll employee fields so they are only available to appropriate HR users. It prevents errors caused by payroll-related information appearing in the public employee profile where it should not be accessible.

Original PR description

Issues:
The model hr.employee requires the group hr.group_hr_user for fields that are not accessible in the employee public profile. The new fields missed the groups.
https://runbot.odoo.com/web#id=61373&view_type=form&model=runbot.build.error&menu_id=405&cids=1

Fix:
Adds the missing groups on the fields
`l10n_au_super_account_ids,super_account_warning`
on h.employee.

#payroll#employees#access rights

[FIX] pos_preparation_display: wrong Ordering of items

PR #60238

Enterprisemasterpos_preparation_display

This fixes an issue where items could appear in the wrong order on the preparation display when starting a database. Staff will see orders in the intended sequence, reducing confusion during preparation workflows.

Original PR description

Make the sequence ordered works in preparation display when starting a db

#point-of-sale#preparation-display#ordering

[DRAFT] [FIX] planning: fix the issue when resource is working without calendar

PR #60295

Enterprisemasterplanning

Grouping planning shifts by role no longer fails when an employee has no working calendar assigned. This keeps planning views usable even when employee schedule information is incomplete.

Original PR description

Steps to Reproduce:
----------
 - Install the planning module.
 - Navigate to the employee app.
 - Create an employee without a working calendar.
 - Navigate to the planning app.
 - Create a shift.
 - Try to group shifts by role.

Issue:
-------
   When trying to group shifts by role, a traceback occurs if an employee is without
  a working calendar.

Cause
-----
   The traceback arises due to the inability to find work intervals for resources without
    a working calendar.

Solution:
----------
   If a resource has a working calendar, the system retrieves work intervals; otherwise,
  it sets the intervals to 0.

task-3858539

#planning#employees#calendar#gantt

[FIX] planning: only compute work hours when group by resource > ...

PR #60182

EnterprisemasterplanningMEDIUM

Fixed an issue that could prevent the Planning schedule from loading when viewed by role. The system now skips a work-hours calculation when the schedule is not grouped by resource, avoiding an error and allowing planners to access the view normally.

Original PR description

Before this commit, when only planning app is installed and the user goes to Planning > Schedule > By Role, a traceback is raised because the resource_id is not found inside work intervals fetched. The reason is because `this.row.resId` is the resource id only if the first group is resource_id and not something else and so when the group by is `role_id > resource_id` the `resId` will return the role id and not the resource id. It would mean the compute work hours should not be done when the group by does not start by resource.

This commit avoids computing the work hours when the progressField is not a employee, that is, when the group by does not start by resource_id.

Affected version(s): master

Steps to reproduce the issue:
============================
1. Install planning app
2. Go to planning > Schedule > By Role

Current Behavior:
================
A traceback is occured because a role id is not found inside work intervals per resource id.

Expected Behavior:
=================
The Gantt view should be loaded without any issue.

runbot-61438

X-original-commit: 5831c225

#planning#schedule#gantt#roles

Issues: The model hr.employee requires the group hr.group_hr_user for fields that are not accessible in the employee public profile. The new fields missed the groups. https://runbot.odoo.com/web#id=61373&view_type=form&model=runbot.build.error&menu_id=405&cids=1 Fix: Adds the missing groups on the fields `l10n_au_super_account_ids,super_account_warning` on h.employee.

Steps to Reproduce: ---------- - Install the planning module. - Navigate to the employee app. - Create an employee without a working calendar. - Navigate to the planning app. - Create a shift. - Try to group shifts by role. Issue: ------- When trying to group shifts by role, a traceback occurs if an employee is without a working calendar. Cause ----- The traceback arises due to the inability to find work intervals for resources without a working calendar. Solution: ---------- If a resource has a working calendar, the system retrieves work intervals; otherwise, it sets the intervals to 0. task-3858539

Before this commit, when only planning app is installed and the user goes to Planning > Schedule > By Role, a traceback is raised because the resource_id is not found inside work intervals fetched. The reason is because `this.row.resId` is the resource id only if the first group is resource_id and not something else and so when the group by is `role_id > resource_id` the `resId` will return the role id and not the resource id. It would mean the compute work hours should not be done when the group by does not start by resource. This commit avoids computing the work hours when the progressField is not a employee, that is, when the group by does not start by resource_id. Affected version(s): master Steps to reproduce the issue: ============================ 1. Install planning app 2. Go to planning > Schedule > By Role Current Behavior: ================ A traceback is occured because a role id is not found inside work intervals per resource id. Expected Behavior: ================= The Gantt view should be loaded without any issue. runbot-61438 X-original-commit: 5831c225