Friday, November 5, 2021
19 changes · master
New functionality added to Odoo
A new module adds subcontracting information to key manufacturing reports, including Production Analysis and the MRP Cost Structure Report. This helps businesses better understand the role and cost impact of subcontracted work in manufacturing operations.
Original PR description
New module mrp_subcontracting_account_enterprise to add subcontracting information in two reports: - Production Analysis - MRP Cost Structure Report
Enhancements to existing features
Project task views are reordered to make planning tools easier to access, and private tasks are now clearly marked in Gantt popovers. Helpdesk tickets now record cancelled refunds, returns, and repairs, with related notifications shown more cleanly on one line.
Resolved issues and error corrections
The Peru electronic invoicing tests were updated to use the correct VAT code, aligning Enterprise with a related core Odoo fix. This helps keep automated checks accurate and reduces the risk of false test results during future updates.
Miscellaneous changes
Before this commit, when you clicked on "Review" the order lines weren't visible due to the number of control-buttons. To fix this, a "More..." button is displayed if there is more than 3 buttons. When you click on this button, a new modal will display a menu with all controls. Note that we had to find a way to close this popup when you triggered the action. See the related commit in community for more information. Task ID: 2453679 Co-authored-by: Adrien Dieudonné <adr@odoo.com>
Original PR description
Before this commit, when you clicked on "Review" the order lines weren't visible due to the number of control-buttons. To fix this, a "More..." button is displayed if there is more than 3 buttons. When you click on this button, a new modal will display a menu with all controls. Note that we had to find a way to close this popup when you triggered the action. See the related commit in community for more information. Task ID: 2453679 Co-authored-by: Adrien Dieudonné <adr@odoo.com> Forward-Port-Of: odoo/enterprise#22124
Original PR description
This PR will bring miscellaneous generic improvements to project and helpdesk: | Module | Current behavior | Desired behavior after merge |…
This PR will bring miscellaneous generic improvements to project and helpdesk: | Module | Current behavior | Desired behavior after merge | |----------|------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| | project | The project tasks views are in this order: kanban, list, calendar, pivot, graph, activity, gantt, map | The views will be in this order: kanban, list, calendar, gantt, map, pivot, graph, activity | | project | The "Project" field is left blank for private tasks in the gantt view popover.| The field will indicate 'fa-lock private'| | helpdesk | A notification is sent to the chatter of a ticket in the following cases: refund posted, return done, repair done | A notification will also be posted in case of a cancelled refund, return or repair| | helpdesk | The chatter notifications are displayed over two lines in the following cases: refund posted, refund cancelled, return done, return cancelled, repair done, repair cancelled | These notifications will be displayed on a single line| Related: odoo/odoo#77870 Task-2657697
This fix prevents the map view from continuing background requests after a user leaves or closes it. It reduces unnecessary server activity and helps avoid errors or instability when navigating away from map screens.
Original PR description
Before this commit, it could happen that the model makes a rpc while the view is unmounted. This commit fixes it by stopping the execution after each await if component is unmounted.
[FIX] website_delivery_ups: fix portal ups number account * IMPACTED VERSIONS 14.0+ * HOW TO REPRODUCE - have the modules portal and website_delivery_ups installed - go to the url /my/account - type any text in the UPS Number Account input and confirm * PROBLEM The following error occur: `Unknown field 'property_ups_carrier_account'` * CAUSE The field is not properly named in `enterprise/website_delivery_ups/controllers/main.py` `partner_ups_carrier_account` is
Original PR description
[FIX] website_delivery_ups: fix portal ups number account * IMPACTED VERSIONS 14.0+ * HOW TO REPRODUCE - have the modules portal and website_delivery_ups installed - go to the url /my/account - type any text in the UPS Number Account input and confirm * PROBLEM The following error occur: `Unknown field 'property_ups_carrier_account'` * CAUSE The field is not properly named in `enterprise/website_delivery_ups/controllers/main.py` `partner_ups_carrier_account` is added to OPTIONAL_BILLING_FIELDS instead of `property_ups_carrier_account` * FIX - Add the correct field name to OPTIONAL_BILLING_FIELDS: `property_ups_carrier_account` - Add the error handling in the template - Mark the label as optional in the template TASK-ID: 2674040 Forward-Port-Of: odoo/enterprise#22126 Forward-Port-Of: odoo/enterprise#21807
It is often more useful to search a mandate by its partner name or by its IBAN account number rather than its internal reference. opw-2684328 Forward-Port-Of: odoo/enterprise#22115
Original PR description
It is often more useful to search a mandate by its partner name or by its IBAN account number rather than its internal reference. opw-2684328 Forward-Port-Of: odoo/enterprise#22115
This PR are the follow-up of #19483 PR to fix the various points to finalize the feature for the v.15. These following points are only done in project sharing feature: - display the planned date begin in kanban view. - hide the phone and address of the partner: because the partner - remove some stat buttons because this buttons was disabled and bring no more information. - display the material button if no material is added in the task. - allow the collaborator to edit planned dates
Original PR description
This PR are the follow-up of #19483 PR to fix the various points to finalize the feature for the v.15. These following points are only done in project sharing feature: - display the planned date begin in kanban view. - hide the phone and address of the partner: because the partner - remove some stat buttons because this buttons was disabled and bring no more information. - display the material button if no material is added in the task. - allow the collaborator to edit planned dates task-2633229 Forward-Port-Of: odoo/enterprise#21155
Changes in the way id's are computed for the tax report broke the way lines are fetched for the hmrc vat obligation system. opw-2683634 Forward-Port-Of: odoo/enterprise#22116
Original PR description
Changes in the way id's are computed for the tax report broke the way lines are fetched for the hmrc vat obligation system. opw-2683634 Forward-Port-Of: odoo/enterprise#22116
Current Behaviour : In the barcode app, when using the 'Print delivery slip' button on a delivery order/cog button the picking slip was printed instead. Behaviour after PR : The 'Print delivery slip' button correctly print the delivery slip. opw-2683901 Forward-Port-Of: odoo/enterprise#22102
Original PR description
Current Behaviour : In the barcode app, when using the 'Print delivery slip' button on a delivery order/cog button the picking slip was printed instead. Behaviour after PR : The 'Print delivery slip' button correctly print the delivery slip. opw-2683901 Forward-Port-Of: odoo/enterprise#22102
Some barcode readers are unable to handle FNC1 separators, therefore let's remove them from our demo GS1 datamatrices and use the max number of digits instead (so they still work). Followup to Task: 2623434 Forward-Port-Of: odoo/enterprise#22021
Original PR description
Some barcode readers are unable to handle FNC1 separators, therefore let's remove them from our demo GS1 datamatrices and use the max number of digits instead (so they still work). Followup to Task: 2623434 Forward-Port-Of: odoo/enterprise#22021
purpose of this commit is when hr_timesheet is installed after the appointment module it will override the 'get_groupby_mapping' because of the same name of the method for this reason appointment's groupby is not working properly so change the method name in that module. task-2679810 Forward-Port-Of: odoo/enterprise#21951
Original PR description
purpose of this commit is when hr_timesheet is installed after the appointment module it will override the 'get_groupby_mapping' because of the same name of the method for this reason appointment's groupby is not working properly so change the method name in that module. task-2679810 Forward-Port-Of: odoo/enterprise#21951
Small fix/improvement: 1. Make "Allocation" button show in "i" form view only when moves to allocate to. (i.e. match community behavior) 2. Commit changes when "i" button is clicked on. This is due to "Allocation" button opening a "new" window when opening the action. After OWL-ification, the default behavior when this occurs is to wipe any not committed changes. Obviously we do not want to lose our work when clicking on this button. Task: 2632884 COM PR: odoo/odoo#76411 Forward-Port-Of
Original PR description
Small fix/improvement: 1. Make "Allocation" button show in "i" form view only when moves to allocate to. (i.e. match community behavior) 2. Commit changes when "i" button is clicked on. This is due to "Allocation" button opening a "new" window when opening the action. After OWL-ification, the default behavior when this occurs is to wipe any not committed changes. Obviously we do not want to lose our work when clicking on this button. Task: 2632884 COM PR: odoo/odoo#76411 Forward-Port-Of: odoo/enterprise#20805
# Purpose Fix various behavior in Appointment # Specifications * Auto publish on duplicate: For appointment type, we don't want to copy the is_published field. When we duplicate an appointment type, the category is copied. With the category copied the default category is not used and so the appointment type was auto published by the default_get method. To avoid this, we set manually to False the is_published field when we copy any category of appointment type. Also when we c
Original PR description
# Purpose Fix various behavior in Appointment # Specifications * Auto publish on duplicate: For appointment type, we don't want to copy the is_published field. When we duplicate an appointment type,…
# Purpose
Fix various behavior in Appointment
# Specifications
* Auto publish on duplicate:
For appointment type, we don't want to copy the is_published field. When we
duplicate an appointment type, the category is copied. With the category copied
the default category is not used and so the appointment type was auto published
by the default_get method.
To avoid this, we set manually to False the is_published field when we copy
any category of appointment type. Also when we create/write an appointment
type (custom or work_hours), we auto publish it.
The goal is when we create a custom or work_hours to auto publish it on the
website (by the user flow or with the code). We keep the default behavior of
the copy of is_published for all categories.
* Allow creation of custom appointment from the invitations menu
* Fix traceback in default_get when creating custom appointment type
* Check if there is a unique slot before computing the duration of a custom
appointment type
See sub commits for more details.
Task-2645163
Forward-Port-Of: odoo/enterprise#20901Before this commit, when the client meets an issue with EasyPost, they get an uncomplete explanation. For example when EasyPost gives this response: `{"error":{"code":"PARAMETER.INVALID_TYPE","message":"Wrong parameter type.","errors":[{"field":"quantity","message":"must be greater than or equal to 1"}]}}` Odoo raised the UserError containing only the `message`: "Wrong parameter type". With this information, the client does not have any idea of what is wrong. Following the easypost API,
Original PR description
Before this commit, when the client meets an issue with EasyPost, they get an
uncomplete explanation.
For example when EasyPost gives this response:
`{"error":{"code":"PARAMETER.INVALID_TYPE","message":"Wrong parameter type.","errors":[{"field":"quantity","message":"must be greater than or equal to 1"}]}}`
Odoo raised the UserError containing only the `message`: "Wrong parameter type".
With this information, the client does not have any idea of what is wrong.
Following the easypost API, We can see that the error object is not just made
of the message (https://www.easypost.com/docs/api#error-object).
With the content of the `errors` field, this is way clearer.
opw-2619670
Forward-Port-Of: odoo/enterprise#21865
Forward-Port-Of: odoo/enterprise#21758When trying to deliver a product with EasyPost, if the quantity is decimal, it will lead to an error message: > Easypost returned an error: Wrong parameter type. > - quantity: must be a whole number According to EasyPost Documentation, `CustomsItem.quantity` should be a float. However, considering the EasyPost server response and the confirmation from EasyPost Support: > The value for this field as the error message says, needs to be a whole number, there cannot be a decimal in it. I c
Original PR description
When trying to deliver a product with EasyPost, if the quantity is decimal, it will lead to an error message: > Easypost returned an error: Wrong parameter type. > - quantity: must be a whole number According to EasyPost Documentation, `CustomsItem.quantity` should be a float. However, considering the EasyPost server response and the confirmation from EasyPost Support: > The value for this field as the error message says, needs to be a whole number, there cannot be a decimal in it. I can make a note of the option type saying "float" to pass on to correct the documentation. `quantity` should actually be a number OPW-2619670 Forward-Port-Of: odoo/enterprise#22083 Forward-Port-Of: odoo/enterprise#22032
Currently, the XML export for the tax report doesn't remove dots or white spaces in VAT numbers, which can lead to problems during the file validation. It didn't handle the '&' character properly in the representative name either. This fixes those issues. Forward-Port-Of: odoo/enterprise#22057
Original PR description
Currently, the XML export for the tax report doesn't remove dots or white spaces in VAT numbers, which can lead to problems during the file validation. It didn't handle the '&' character properly in the representative name either. This fixes those issues. Forward-Port-Of: odoo/enterprise#22057
[FIX] chart_panel: correctly update state property [FIX] selection_input: fix single range inputs [FIX] edition/selection_input: component loss of focus was not reflected on the plugins [FIX] position hook: update .o-spreadsheet position on mounted [IMP] tokenizer, parser: recognize #REF [REF] highlights: remove highlight plugin state Forward-Port-Of: odoo/enterprise#22097
Original PR description
[FIX] chart_panel: correctly update state property [FIX] selection_input: fix single range inputs [FIX] edition/selection_input: component loss of focus was not reflected on the plugins [FIX] position hook: update .o-spreadsheet position on mounted [IMP] tokenizer, parser: recognize #REF [REF] highlights: remove highlight plugin state Forward-Port-Of: odoo/enterprise#22097
The field name is already given is note so we change the name note to operation_note. opw-2545355 Forward-Port-Of: odoo/enterprise#20313
Original PR description
The field name is already given is note so we change the name note to operation_note. opw-2545355 Forward-Port-Of: odoo/enterprise#20313