Monday, May 9, 2022
4 changes · master
Resolved issues and error corrections
Project task analysis now calculates average ratings correctly by matching ratings to the right task and averaging them instead of adding them together. This gives managers more reliable task satisfaction reporting and adds test/demo coverage to prevent the issue from returning.
Original PR description
Before this commit: - Join between task and rating is made on parent_res_id - Displayed value is the sum of tasks average_rating - No Unit test to detect this anomalie - Each task is rated one time so average_rating and last_rating are the same After this commit: - Join is made on res_id which is the task_id - Displayed value is the avg of tasks average_rating - Unit test added to cover mesaures calculation - New demo record added to let average_rating be different from last_rating Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a dashboard issue where adding a new action could erase the dashboard's existing layout or previously added actions. Users can now add multiple actions to a dashboard without losing the current board state.
Original PR description
Before this commit, the code of the `add_to_dashboard` method did not go through the get_view override of the board model. Because of that, it did not get the arch of the current board, which means that each add_to_dashboard call was actually a complete reset: it was not possible to add an action without removing the current board state. For reference, this was caused recently by a change in commit b03c227e885efa. The fix is basically a localized revert of that commit. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Time off requests now show whole-day totals consistently, even when an employee or manager uses a different time zone than the company context. This prevents misleading fractional leave balances such as 2.69 days for a 3-day absence.
Original PR description
When the user is set in another timezone than the context timezone, the first or last work interval retrieved to calculate the number of days between two dates is starting later or ending earlier depending on the user timezone. The number of days displayed between two dates is therefore not an integer. e.g. A time off taken between 08/06/2021 and 10/06/2021 (timezone in the context is Europe/Brussels) will give: - Number of days: 3 days if the user is in Europe/Brussels - Number of days: 2.69 if the user is in Asia/Calcutta (first work interval starting later) - Number of days: 2.5 if the user is in US/Pacific (last work interval ending earlier) task-2646655 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Automated Amazon sales and subscription cancellation flows now bypass the manual cancellation wizard. This prevents background processes from being interrupted by a user-facing prompt and helps cancellations complete reliably.
Original PR description
`action_cancel` opens the cancellation wizard, but we don't want to open it in an automated flow. So we need to use `_action_cancel` instead. task-2660895 See also: - https://github.com/odoo/odoo/pull/81569