Daily updates from Odoo
Navigate
Branch
Wednesday, February 9, 2022
10 changes
Enhancements to existing features
Skill and appraisal dropdowns now show extra context directly in the list, such as skill progression values and skill types. This makes it easier for users to choose the right skill or level without opening each option to inspect its details.
Original PR description
Description of the issue/feature this PR addresses: When you want to add/select new skills, it could be more clear. Current behavior before PR: When you want to change a skill level, you have to select a skill level to see its progression value Desired behavior after PR is merged: - The progression value is displayed beside the skill level in the dropdown list. - In the appraisal module, the same thing applies to skills, which also feature the skill type in the dropdown list. task: #2719642 [Skills] Overwrite name_get() community PR : https://github.com/odoo/odoo/pull/82202
Code cleanup and technical improvements
The Enterprise navigation experience has been refreshed as part of the Odoo 16 redesign, especially for mobile users. This makes menus such as company switching, user options, and the main navigation feel more consistent with the broader product interface.
Original PR description
requires: - https://github.com/odoo/odoo/pull/83501 > merged - https://github.com/odoo/enterprise/pull/23848 > merged community: - https://github.com/odoo/odoo/pull/82434
Miscellaneous changes
Before this commit, when the "Invoicing Policy" in Timesheet app (that "sale.invoiced_timesheet" param) is equal to "approved", only the validated timesheets should be visible for the portal user if he has access to the related task. In project sharing, it is not the case, the portal user sees no timesheets related to the task when the `sale.invoiced_timesheets == 'approved'`. This commit fixes the issue to show the validated timesheets related to a task when the user is in the task for
Original PR description
Before this commit, when the "Invoicing Policy" in Timesheet app (that "sale.invoiced_timesheet" param) is equal to "approved", only the validated timesheets should be visible for the portal user if he has access to the related task. In project sharing, it is not the case, the portal user sees no timesheets related to the task when the `sale.invoiced_timesheets == 'approved'`. This commit fixes the issue to show the validated timesheets related to a task when the user is in the task form view via the project sharing feature. (Bug discovered during the development of task-2648955) X-original-commit: e16f25001427330706438b10eb9a165aed4ebb41 Forward-Port-Of: odoo/enterprise#24171 Forward-Port-Of: odoo/enterprise#24159
Forward-Port-Of: odoo/enterprise#24178
Original PR description
Forward-Port-Of: odoo/enterprise#24178
Invoice line description included in XML must be 250 characters at most [1]. [1] (p18) https://www.sunat.gob.pe/legislacion/superin/2017/anexoIX-117-2017.pdf Forward-Port-Of: odoo/enterprise#24003 Forward-Port-Of: odoo/enterprise#23981
Original PR description
Invoice line description included in XML must be 250 characters at most [1]. [1] (p18) https://www.sunat.gob.pe/legislacion/superin/2017/anexoIX-117-2017.pdf Forward-Port-Of: odoo/enterprise#24003 Forward-Port-Of: odoo/enterprise#23981
Steps to reproduce: - Go to Field Service App from an Android device - Create a new task - Select a title and a customer - Click on the smart button "Products" - Add more than 9 characters or some alphabetical characters Result: The alphabetical characters are visible and is possible to add more than 9 characters. The validation is not performed. Expected result: As on a desktop browser it shouldn't be possible to add more than 9 digits and the shown number should be a natural (no
Original PR description
Steps to reproduce: - Go to Field Service App from an Android device - Create a new task - Select a title and a customer - Click on the smart button "Products" - Add more than 9 characters or some…
Steps to reproduce: - Go to Field Service App from an Android device - Create a new task - Select a title and a customer - Click on the smart button "Products" - Add more than 9 characters or some alphabetical characters Result: The alphabetical characters are visible and is possible to add more than 9 characters. The validation is not performed. Expected result: As on a desktop browser it shouldn't be possible to add more than 9 digits and the shown number should be a natural (no alphabetical characters or special characters). Keypress events are not working on Android and also the KeyboardEvent from an Android Virtual Keyboard doesn't return the pressed key identifier (keyCode). I switched the span contenteditable with a simpler input element. Now the UI doesn't prevent the insertion of an invalid number, but in this case the value is highlighted by a red color. The server will check and save the new value only if valid. opw-2710590 Forward-Port-Of: odoo/enterprise#23053
Currently: - The wizard for the annual report does not contain the complete set of tax fields that are required. - The form view is very limited and does not allow editing Desired: - Add missing tax grid fields and a possibility to add appendix lines to export a full annual VAT report - Add state (XML exported/not exported), editing is blocked when the report is exported, can be reset with the "reset" button - Add a possibility for users to track changes in the report in the chatter for
Original PR description
Currently: - The wizard for the annual report does not contain the complete set of tax fields that are required. - The form view is very limited and does not allow editing Desired: - Add missing tax grid fields and a possibility to add appendix lines to export a full annual VAT report - Add state (XML exported/not exported), editing is blocked when the report is exported, can be reset with the "reset" button - Add a possibility for users to track changes in the report in the chatter for auditing purposes - Remove the wizard, moving the entire annual report creation/editing/exporting process to the form view Task ID: 2694161 Forward-Port-Of: odoo/enterprise#24099 Forward-Port-Of: odoo/enterprise#22621
Steps : Create a Rental Order. Add a SOL with Product Meeting Room. In the wizard, as Dates : Tomorrow 00:00 - Tomorrow 23:00. Validate. Issue : See, in SOL Description : "Meeting Room 02/08/2022 00:00:00 to 02/08/2022 23:00:00". Expected : "...to 23:00:00". Cause : If picking date is equal to return date, the date should only be displayed once. Yet, the dates are not timezoned for this check. Fix : Take timezone into account to check this condition. opw: 2746372 Forward-Po
Original PR description
Steps : Create a Rental Order. Add a SOL with Product Meeting Room. In the wizard, as Dates : Tomorrow 00:00 - Tomorrow 23:00. Validate. Issue : See, in SOL Description : "Meeting Room 02/08/2022 00:00:00 to 02/08/2022 23:00:00". Expected : "...to 23:00:00". Cause : If picking date is equal to return date, the date should only be displayed once. Yet, the dates are not timezoned for this check. Fix : Take timezone into account to check this condition. opw: 2746372 Forward-Port-Of: odoo/enterprise#24118 Forward-Port-Of: odoo/enterprise#24085
Steps : Download Timesheets. Note Admin > Work Information > Working Hours : Standard 40 hours/week. Go to Timesheets > All Timesheets > Month and search Employee : Admin. Go to previous untill you reach a month with a week day as last day. Erase all his timesheets. Issue : Say number of working days = 23 => worked hours = 23d * 8h/d = 184h The number written in red next to Admin's name is -176.00. It represents : worked hours (0,00) - working hours. Which means working hours = 176.
Original PR description
Steps : Download Timesheets. Note Admin > Work Information > Working Hours : Standard 40 hours/week. Go to Timesheets > All Timesheets > Month and search Employee : Admin. Go to previous untill you reach a month with a week day as last day. Erase all his timesheets. Issue : Say number of working days = 23 => worked hours = 23d * 8h/d = 184h The number written in red next to Admin's name is -176.00. It represents : worked hours (0,00) - working hours. Which means working hours = 176. Which means working days = 176h / 8h/d = 22. Which is wrong. Cause : get_timesheet_and_working_hours_for_employees calls _get_work_days_data_batch giving it end_datetime with time = 0h00. Fix : Call it with time = max. opw: 2742651 Forward-Port-Of: odoo/enterprise#24157
The commit https://github.com/odoo/odoo/commit/ccf6973b394d045a90a8bec64c06439b9dc41305 modified the timesheets' partner_ids to be computed and use the project's or task's customer, but forgot about the helpdesk tickets. This commit should add the helpdesk tickets' customer into account. Now, the priority order for choosing the partner_id is Ticket > Task > Project. opw-2690184 Forward-Port-Of: odoo/enterprise#24156 Forward-Port-Of: odoo/enterprise#23796
Original PR description
The commit https://github.com/odoo/odoo/commit/ccf6973b394d045a90a8bec64c06439b9dc41305 modified the timesheets' partner_ids to be computed and use the project's or task's customer, but forgot about the helpdesk tickets. This commit should add the helpdesk tickets' customer into account. Now, the priority order for choosing the partner_id is Ticket > Task > Project. opw-2690184 Forward-Port-Of: odoo/enterprise#24156 Forward-Port-Of: odoo/enterprise#23796