Thursday, November 3, 2022
7 changes · master
Enhancements to existing features
The Documents app now uses a purpose-built reference field for linking documents to related records. This makes the underlying data model more reliable and easier to maintain, with no expected change to everyday user workflows.
Original PR description
Use the special field Many2oneRefernece specifically made for dynamic many2ones instead of a basic integer field. TaskId-2093709
Resolved issues and error corrections
This update adjusts the Master Production Schedule screen so its filter controls work consistently with automated checks and expected interface behavior. It helps prevent issues when users or tests apply filters in the control panel, with no expected change to day-to-day workflows.
Original PR description
When a Click Everywhere test filters in the control panel, it assumes with_search is used for the view. In this commit, we make Mrp_mps also uses with_search to pass the test.
Miscellaneous changes
Steps to reproduce: - Create a partner "user 1" and then a user "user 2" with the same email address "test@test.com" - When connected as user 2 create a ticket Current behavior: The ticket is assigned to "user 1" Expected behavior: The ticket is assigned to "user 2" Explanation: To get the partner the code used to only take the first partner in the list of partners with the mail written in the form. Now it will prioritise the partner corresponding to the connected user if it is i
Original PR description
Steps to reproduce: - Create a partner "user 1" and then a user "user 2" with the same email address "test@test.com" - When connected as user 2 create a ticket Current behavior: The ticket is assigned to "user 1" Expected behavior: The ticket is assigned to "user 2" Explanation: To get the partner the code used to only take the first partner in the list of partners with the mail written in the form. Now it will prioritise the partner corresponding to the connected user if it is its email address. opw-3007846 Forward-Port-Of: odoo/enterprise#33405 Forward-Port-Of: odoo/enterprise#32503
This fixes a crash that could happen when adding a sales subscription line before a currency was set. Users can now continue creating subscription orders in that sequence without being blocked by an error.
Original PR description
Since 442899cbf39111f399e90f466f669a321f1da8ea when a sol is added we check if the value is rounded to 0 according to the currency. If there is no currency the rounding would raise an error as you cannot round without a non-positive rounding.
Current behavior: When we open payments to send via ABA from the accounting dashboard, there is a the difference in the number of records from the list view and dashboard which happens to be the same. Expected behavior: When we open payments to send via ABA from the accounting dashboard, the number of records should be the same in the dashboard and list view. Reason for that: We have changed the domain of the dashboard view but the list view's domain is not updated. The improvemen
Original PR description
Current behavior: When we open payments to send via ABA from the accounting dashboard, there is a the difference in the number of records from the list view and dashboard which happens to be the same. Expected behavior: When we open payments to send via ABA from the accounting dashboard, the number of records should be the same in the dashboard and list view. Reason for that: We have changed the domain of the dashboard view but the list view's domain is not updated. The improvement in the domain is from this PR (https://github.com/odoo/enterprise/pull/20177). But the same thing is not reflected on the list view's domain. Fix To update the domain of the filter of the list view. Task:- 3017513 Forward-Port-Of: odoo/enterprise#33476
If there is no company for operation_id of mrp_workorder then quality_point_ids should be same company of mrp_workorder's company Steps to reproduce - - When production orders is in draft/confirm stage and bom_id is set but workorder is not created for that bill of material then during upgrade process workorder is created using _create_workorder() method while creating workorder there is quality_point_ids field is set and that is computed based on quality_point_ids of operation
Original PR description
If there is no company for operation_id of mrp_workorder then quality_point_ids should be same company of mrp_workorder's company Steps to reproduce - - When production orders is in draft/confirm…
If there is no company for operation_id of mrp_workorder then quality_point_ids should be same company of mrp_workorder's company Steps to reproduce - - When production orders is in draft/confirm stage and bom_id is set but workorder is not created for that bill of material then during upgrade process workorder is created using _create_workorder() method while creating workorder there is quality_point_ids field is set and that is computed based on quality_point_ids of operation_id field. - But if in case, operation_id(mrp.routing.workcenter) have company_id null then quality_points are browsed from all company, and computing quality_point_ids of workorder is based on product_ids, filtering quality_point based on product_ids if quality_point's product_ids is null or product_ids is in workorder's related production's product_id. - That's why, the quality point's company id may differ from workorder's company id. Issue - - Due to this is different company issue in workorder and quality_point occurs multi-company issue for quality_check and quality_point, while creating quality_check of those workorder. Solution - - For which here we have added one condition in it, that is checking a company_id of workorder and quality_point. If workorder's company and quality_point's company are same then only those quality_point is set to workorder. opw - 2919671 Forward-Port-Of: odoo/enterprise#30233
Some parts of the depreciation schedule were not dark mode compatible. Forward-Port-Of: odoo/enterprise#33500
Original PR description
Some parts of the depreciation schedule were not dark mode compatible. Forward-Port-Of: odoo/enterprise#33500