Daily updates from Odoo
Navigate
Branch
Friday, April 22, 2022
15 changes
Enhancements to existing features
The Planning analysis report now gives managers clearer visibility into resource capacity, utilization, billable versus non-billable assignments, and employee time off. This helps teams spot overbooked or available people, balance profitable work, and better understand how planned hours are distributed.
Original PR description
Improve the Planning analysis report by providing additional measures on: the capacity and utilization of resources -> goal: easily identify who is still available or who has been allocated too much work the ratio of billable vs. non-billable hours assigned -> goal: making sure that a resource is profitable and that the work he is assigned is well balanced the time off taken by the employees -> goal: help the user understand the distribution of hours Because these measures are quite complex to implement, we will be creating a new report for this task instead of relying on planning.slot. See task-2742620
The Documents spreadsheet component has been updated to the latest spreadsheet engine version. This brings maintenance improvements around chart handling, sheet management, and formatting checks, helping keep spreadsheet features stable and aligned with the upstream product.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/a1d601e3 [FIX] package.json: check tools and xml code formatting https://github.com/odoo/o-spreadsheet/commit/6efc0328 [REF] package.json: move chart.js as npm dependency https://github.com/odoo/o-spreadsheet/commit/27869f43 [REF] tests: introduce moveSheet helper https://github.com/odoo/o-spreadsheet/commit/5ee692df [REF] sheet: simplify sheets getters https://github.com/odoo/o-spreadsheet/commit/0ad91f94 [FIX] spreadsheet: fix in package.json
Employees being archived can now receive links to their archived documents even if they do not have a linked system user account. This helps ensure departing employees can still access the documents intended for them and reduces manual follow-up for HR teams.
Original PR description
Purpose: When we archive employees, we send them link for archived documents. It is possible that an employee is not linked with an user. Regardless, we should be able to send a link to employee. task - 2806702
This update adapts spreadsheet document and Studio dialog windows to a newer shared dialog system. It helps keep these screens compatible with the latest platform changes without changing the main business workflow.
Original PR description
enterprise part of [odoo/#89113](https://github.com/odoo/odoo/pull/89113)
Resolved issues and error corrections
This fix prevents the Belgian payroll working schedule change wizard from failing when no start date is available. It uses today's date as a safe fallback, helping HR users continue schedule changes without interruption.
Original PR description
When the _compute_new_allocation method is called from _compute_time_off_allocation, the date_start is not defined when the wizard is open. This commit takes today as date_start if not defined
Code cleanup and technical improvements
Manufacturing-related records now rely on automatic calculations instead of manually creating related movement data. This reduces maintenance complexity and helps keep production and quality demo data aligned with the updated manufacturing workflow.
Original PR description
Community PR: odoo/odoo#83576
Miscellaneous changes
Step to reproduce: - Create a ticket with user named portal - Write a message - Archive the ticket - As portal user : Go to ticket portal and filter by `last message from support` Current behaviour: - Error 500/Traceback - We try to access data not in the active ticket dict Behaviour after PR: - Only compute on ticket in both active and last_message dict opw-2820002 Forward-Port-Of: odoo/enterprise#26432
Original PR description
Step to reproduce: - Create a ticket with user named portal - Write a message - Archive the ticket - As portal user : Go to ticket portal and filter by `last message from support` Current behaviour: - Error 500/Traceback - We try to access data not in the active ticket dict Behaviour after PR: - Only compute on ticket in both active and last_message dict opw-2820002 Forward-Port-Of: odoo/enterprise#26432
When going on a Follow-Up reports, you can change the status of a client (the small ball on the left of their name). In the dropdown, we don't see the "Bad Debtor" option. Step to reproduce the issue: 1) Install the Accounting app 2) Go to a Follow-Up reports and try to change their status You cannot fully see the "Bad Debtor" option. Solution: During a previous commit (b11141717719744ba143e3d77a5ef883b63c7124), an `overflow:hidden` was added into the CSS, it should rather be a `over
Original PR description
When going on a Follow-Up reports, you can change the status of a client (the small ball on the left of their name). In the dropdown, we don't see the "Bad Debtor" option. Step to reproduce the issue: 1) Install the Accounting app 2) Go to a Follow-Up reports and try to change their status You cannot fully see the "Bad Debtor" option. Solution: During a previous commit (b11141717719744ba143e3d77a5ef883b63c7124), an `overflow:hidden` was added into the CSS, it should rather be a `overflow:visible` as the dropdown will overlap with other divs. opw-2816612 Forward-Port-Of: odoo/enterprise#26444
Looking at runbot and newly created 15.1 DBs, it seems some terms in Spanish (MX) are wrongly translated. opw-2796876 Forward-Port-Of: odoo/enterprise#26491 Forward-Port-Of: odoo/enterprise#26322
Original PR description
Looking at runbot and newly created 15.1 DBs, it seems some terms in Spanish (MX) are wrongly translated. opw-2796876 Forward-Port-Of: odoo/enterprise#26491 Forward-Port-Of: odoo/enterprise#26322
web_studio overrides the _name_check constraint on IrModelField but the parent validation is skipped. This allows the creation of custom fields that have wrong characters including the space character, which later causes an error when 'reflect fields' is called and tries to add model_data records with an xml_id that includes the field name. An sql constraint on xml_id, 'name_nospaces', causes failure. A migration script should fix the records that violate the following: - prefix is `x_
Original PR description
web_studio overrides the _name_check constraint on IrModelField but the parent validation is skipped. This allows the creation of custom fields that have wrong characters including the space character, which later causes an error when 'reflect fields' is called and tries to add model_data records with an xml_id that includes the field name. An sql constraint on xml_id, 'name_nospaces', causes failure. A migration script should fix the records that violate the following: - prefix is `x_` - no spaces in the field name Other restrictions in the base model field name are not automatically fixed. Also, databases with existing records that violate the base constraint will throw errors when attempting to upgrade the modules on the same version. Forward-Port-Of: odoo/enterprise#25605
In task 2759601 some improvements to the dashboard notes were merged. However, after some time a change made by the js team or the editor team started causing tracebacks in the editor with every keystroke. The main issue was that in the initial implementation the mode of the view was changed from readonly to edit without reinitializing the widget. This commit changes the template so that the widget is destroyed and initialized again if the mode is changed. Also, tests are added in order to
Original PR description
In task 2759601 some improvements to the dashboard notes were merged. However, after some time a change made by the js team or the editor team started causing tracebacks in the editor with every keystroke. The main issue was that in the initial implementation the mode of the view was changed from readonly to edit without reinitializing the widget. This commit changes the template so that the widget is destroyed and initialized again if the mode is changed. Also, tests are added in order to prevent this functionality from breaking again. task-2822711 Forward-Port-Of: odoo/enterprise#26144
task-2758779 Forward-Port-Of: odoo/enterprise#26438 Forward-Port-Of: odoo/enterprise#24820
Original PR description
task-2758779 Forward-Port-Of: odoo/enterprise#26438 Forward-Port-Of: odoo/enterprise#24820
Before this commit, the sale_renting report was failing because of the following tag: ``` Template: sale_renting.report_rental_order_document Path: /t/t/div/table/tbody/t/tr/td[2]/span Node: <span t-field="line.pickup_date"/> ``` Forward-Port-Of: odoo/enterprise#26436
Original PR description
Before this commit, the sale_renting report was failing because of the following tag: ``` Template: sale_renting.report_rental_order_document Path: /t/t/div/table/tbody/t/tr/td[2]/span Node: <span t-field="line.pickup_date"/> ``` Forward-Port-Of: odoo/enterprise#26436
Steps to reproduce: - With a company with currency X, and multi-currency activated - Make a vendor bill in currency Y, confirm and pay it - On reconcilation model, the amount is display with the sign of currency X instead of the one of currency Y opw-2690144 Forward-Port-Of: odoo/enterprise#23990
Original PR description
Steps to reproduce: - With a company with currency X, and multi-currency activated - Make a vendor bill in currency Y, confirm and pay it - On reconcilation model, the amount is display with the sign of currency X instead of the one of currency Y opw-2690144 Forward-Port-Of: odoo/enterprise#23990
Step to reproduce: Install appointment Add a required multiline field to an appointment type Create an appointment for this appointment type Expected behavior: There is a star after the multi-line field name Current beahvior: no star Solution: Add the star if required like in the other fields when the question_type!='text' (see a few lines above) opw-2822662 Forward-Port-Of: odoo/enterprise#26269
Original PR description
Step to reproduce: Install appointment Add a required multiline field to an appointment type Create an appointment for this appointment type Expected behavior: There is a star after the multi-line field name Current beahvior: no star Solution: Add the star if required like in the other fields when the question_type!='text' (see a few lines above) opw-2822662 Forward-Port-Of: odoo/enterprise#26269