Tuesday, June 1, 2021
4 changes · master
Enhancements to existing features
This update makes Planning easier to use by improving shift creation, task assignment, schedule sending, templates, roles, and reporting views. It also updates planning reports with clearer time-off and working-hours measures, helping managers better compare planned, unavailable, and actual worked time.
Original PR description
## PURPOSE Generic UX improvements to ease the use of Planning and the onboarding. ### Details - When selecting a task on a shift, set automatically the user assigned to the task to the shift (only…
## PURPOSE
Generic UX improvements to ease the use of Planning and the onboarding.
### Details
- When selecting a task on a shift, set automatically the user assigned to the task to the shift (only applicable if the employee_id field is false)
- An internal user without any access to the Planning app should see all published open shifts if both the default_planning_role_id and planning_role_ids fields on his hr.employee are false
- if one of these fields are set, he should only see the published open shifts for his roles
- Remove the 'allocated time percentage' feature
- In "Timesheet and planning analysis" report:
- Add 'time off' measure that represents the number of working hours during which the employee was on time off.
- Update the 'Difference' to represent the difference between the sum of planning hours and the time off and the effective hours. Calculation: `planned_hours + time off measure - effective_hours`.
- Remove the 'number of working hours' measure.
- In "Planning Analysis" report:
- Add 'time off' measure that represents the number of working hours during which the employee was on time off.
- Add the 'number of working hours' measure.
- Add an 'allocated working hours (%)' measure which should represent the % of (allocated hours + time off) based on the working hours for the selected period.
- Add kanban view to the following menus:
- reporting > planning analysis
- configuration > roles
- configuration > shift templates
- Add an 'active' filter and a corresponding 'archived' filter to the following models: planning.role, planning.slot.template.
- For `planning.slot.template` model:
- Add a *sequence* field, the templates will be ordered on the shift form view accordingly.
- Add a *name* field that represent the "start hour - end hour (x days span)".
- remove the start hour and duration fields in the list view.
- In calendar view of planning.slot model, when the shift is a single day and not an entire day then display the end hour of this shift.
- When the user wants to send the schedule and there are no shifts to send, we replace the blocking error by a red toast notification that states: "There are no shifts to send or publish.".
- In gantt view of `planning.slot` model:
- When the user creates a shift via the form view available in the gantt and want to save it as template, we display the following toast notification when a template is created: "fa-check This shift was successfully saved as a template.".
- the default start/end dates of newly created shifts should be today's date if the period of the gantt view contain the today date otherwise the default start/end dates are the first working day of the company in the period.
- when the user clicks on the "Send schedule" button: display a green toast notification that states 'fa-check The schedule was successfully sent to your employees.'
- In form view of `planning.slot` model:
- the space between the 'repeat' and 'save as template' fields has been removed.
- when setting repeat to true on an existing shift, the default values should be '1 week' and 'forever'.
- Change the helper to 'No shifts found. Let's create one!...' when there are no shifts in the schedule menus.
- Change the helper to: 'No shift templates found. Let's create one!...' when there are no shift templates.
task-2463722Several invite-style email wizards now use a shared composer approach, reducing duplicated logic and making future template updates easier. The change also cleans up outdated or incorrect email template fields, helping messages render more reliably across appraisal, payroll, field service, localization, marketing, and subscription flows.
Original PR description
In this merge we use the new mail.composer.mixin added in community to help designing light invite-like wizards. Using this mixin allows to hide details about jinja-based computation for main fields used when posting messages or sending emails. Notably subject and body computation that was duplicated in several addons are now done in a mixin. It also eases their maintenance or evolution when qweb rendering will be available. It also eases support of lang when necessary. In this merge we also clean some outdated or wrongly-used jinja code bits or fields definition in some templates. Some reordering in files is also performed to help future maintenance of templates. See sub-commits for more details. Task ID-2534550 (Template usage improvement) Task ID-2477164 (Composer mixin)
Aged Receivable and Aged Payable reports now show the original foreign-currency amount and its currency when multi-currency access is enabled. This helps accounting teams review, export, and revalue open balances more easily and accurately.
Original PR description
Aims to assist the user to revalue amounts in the Aged Receivable and Aged Payable Reports when multi currency access is available to the user. 2 columns are added to the AR/AP reports detail - `Amount Currency` and `Currency` export files contain the raw values to improve usability. task [2352602](https://www.odoo.com/web#id=2352602&model=project.task)
The account form has been reorganized to make key information easier to find and manage. Users can now quickly see related taxes through a smart button, and activity tracking has been added so changes are easier to follow over time.
Original PR description
To make the account.account form view usability better, we'll move around the fields, add a new smart button to link the account to the taxes using it as well as add a chatter to keep track of changes. Task id #2481421