Daily updates from Odoo
Navigate
Branch
Tuesday, June 15, 2021
9 changes
Enhancements to existing features
Belgian payroll users can now use a dedicated wizard to recover double pay amounts from payslips. This makes a country-specific payroll adjustment easier to manage and helps reduce manual handling during payroll validation.
Resolved issues and error corrections
This fix improves the layout of action buttons in Odoo notification emails when viewed in Discuss or record chatter. Users should no longer see unnecessary scrollbars inside buttons, making links to records and portal pages easier to read and use.
Original PR description
PURPOSE Currently, if user receive notification in odoo, and open it in Discuss than button is not properly visible and it contain scrollbar in button because of margin and overflow property. SPECIFICATION This PR fixes the issue by improving such templates by using proper puddings on the buttons. Task Id: 2518863
Code cleanup and technical improvements
The spreadsheet pivot side panel has been reorganized so the pivot list and pivot details are handled separately. This internal cleanup makes future enhancements, such as editing pivot filters, easier to add and maintain without changing the current user experience.
Original PR description
The pivot side panel component manages two things: 1) the list of pivots 2) the details of each pivot (domain, groupby, fields, etc.) This is a preliminary work to to allow editing the domain. This feature will add code and logic to the side panel component and we don't want to drift towards a "giant pivot side panel component to rule them all". This commit splits the current component in two components, each with a better defined scope of responsabilities: - one to manage the list of pivots and which pivot details to show - one to actually manage pivot details Task 2296880
Miscellaneous changes
When adding components to a confirmed MO in tablet view, then not processing the full quantity at once and creating a backorder for the remaining quantity, the consumption of the added components in the first backorder is not correct. There was a duplication of the move line of the added components, doubling its used quantity. This duplication came from two situations: - If the additional component is available, there was no move line in the quality check created with the additional comp
Original PR description
When adding components to a confirmed MO in tablet view, then not processing the full quantity at once and creating a backorder for the remaining quantity, the consumption of the added components in the first backorder is not correct. There was a duplication of the move line of the added components, doubling its used quantity. This duplication came from two situations: - If the additional component is available, there was no move line in the quality check created with the additional component. Not seeing this move line, a new one was created in the _next method of mrp_workorder. - If the compoment is not available, no SML is recorded in the quality check but a SML was created in set_qty_producing because no workcenter was registered in the stock move. A second SML was then created in _next. Task-ID: 2447949 Forward-Port-Of: odoo/enterprise#16954
Forward-Port-Of: odoo/enterprise#18991
Original PR description
Forward-Port-Of: odoo/enterprise#18991
During the refactor of mrp, we broke the workorder step by variant (Be able to have workorder step depending of the variant of the production). Fix it by apply a filtered in the compute of `quality_point_ids` of the `mrp.workorder`. task-2557768 Forward-Port-Of: odoo/enterprise#18994 Forward-Port-Of: odoo/enterprise#18719
Original PR description
During the refactor of mrp, we broke the workorder step by variant (Be able to have workorder step depending of the variant of the production). Fix it by apply a filtered in the compute of `quality_point_ids` of the `mrp.workorder`. task-2557768 Forward-Port-Of: odoo/enterprise#18994 Forward-Port-Of: odoo/enterprise#18719
Forward-Port-Of: odoo/enterprise#18910 Forward-Port-Of: odoo/enterprise#18139
Original PR description
Forward-Port-Of: odoo/enterprise#18910 Forward-Port-Of: odoo/enterprise#18139
latam task 567 --- Separate Mipyme documents types tests into a new test class and mark it with tags: not standard and external to do not run the test automatically. Forward-Port-Of: odoo/enterprise#18884
Original PR description
latam task 567 --- Separate Mipyme documents types tests into a new test class and mark it with tags: not standard and external to do not run the test automatically. Forward-Port-Of: odoo/enterprise#18884
…ble revenue Forward-Port-Of: odoo/enterprise#18839
Original PR description
…ble revenue Forward-Port-Of: odoo/enterprise#18839