Daily updates from Odoo
Navigate
Branch
Wednesday, November 24, 2021
8 changes
Enhancements to existing features
This update makes internal adjustments in the Approvals and Sign apps to prepare them for an upcoming interface technology upgrade. There should be no visible change for users, but it helps keep these apps compatible and easier to maintain.
Original PR description
In preparation of using OWL v2 in discuss code Task-2694242 community: https://github.com/odoo/odoo/pull/80094
The messaging chatter panel is no longer shown as a side panel when it appears inside a page/tab area. This keeps page layouts cleaner and avoids misplaced discussion panels in the form view experience.
Original PR description
Purpose ======= Change function _isChatterAside to return false if the chatter is in a page (class contains 'tab-pane') Task-2679537
The appraisal survey screens were aligned with recent survey view updates and a duplicate view definition was removed. This improves consistency and reduces clutter when managing appraisal surveys, especially where many surveys are involved.
Original PR description
PURPOSE When dealing with lot of surveys kanban view is not really optimal and its state based grouping is not really helpful. Indeed we do not have total of each coumn and there is not point adding new states, meaning most surveys hang in the same column. This is not an optimal display. SPECIFICATIONS Update to survey views cleaning and improvements. Task-2388785
Resolved issues and error corrections
This change removes leftover unused code from the Predictive Bills area after an earlier update. It has no expected impact on day-to-day use, but helps keep the system cleaner and easier to maintain.
Original PR description
This should have been removed when forward porting [1] to [2] in master, when removing the DeprecationWarning [1] 0d872f2c93cf31216867948c88cd79a83919ff89 [2] 57a2d4be27920aaf99bc342dd5b15f5d9ecf88dd
A small compatibility module restores the information needed for manufacturing orders to open in the default Gantt view. This prevents upgrade failures for databases that still rely on that planning view when moving to version 15.
Original PR description
Adds a tiny bridge module between `mrp` and `web_gantt`. It adds the missing fields `_start_name` and `_stop_name` for the default Gantt view to work with `mrp.production`. Since in v15 its Gantt view was removed and the default one doesn't work, the databases that make use of it fail to upgrade to v15.
Code cleanup and technical improvements
Spreadsheet collaboration handling was reorganized behind the scenes to make the code easier to maintain and test. This should not change day-to-day behavior for users, but it helps reduce future development risk around spreadsheet features.
Miscellaneous changes
Function `_get_default_gantt_view` doesn't work with `mrp.production` since v15 as the model lacks any of the compatible fields. This is blocking upgrades of databases that use the Gantt view in actions: upg-43176 upg-44647 upg-44733 The related commit: https://github.com/odoo/odoo/commit/876c2c33e8f1f50799cf2af5dfebca13a0c4cd4c Forward-Port-Of: odoo/enterprise#22485
Original PR description
Function `_get_default_gantt_view` doesn't work with `mrp.production` since v15 as the model lacks any of the compatible fields. This is blocking upgrades of databases that use the Gantt view in actions: upg-43176 upg-44647 upg-44733 The related commit: https://github.com/odoo/odoo/commit/876c2c33e8f1f50799cf2af5dfebca13a0c4cd4c Forward-Port-Of: odoo/enterprise#22485
Usecase to reproduce: - Create a Lot1 for product A and B - Add product A in an operation with a workorder step - In tablet view when asking to enter lot name for product A scan the Lot1 Current result: Traceback since it try to add multiple record to a many2one Expected result: Lot 1 is set on the tablet view It happens because on_barcode_scan doesn't check the product while searching the barcode. It would even be possible to set a lot not related to the product. Fix it by addi
Original PR description
Usecase to reproduce: - Create a Lot1 for product A and B - Add product A in an operation with a workorder step - In tablet view when asking to enter lot name for product A scan the Lot1 Current result: Traceback since it try to add multiple record to a many2one Expected result: Lot 1 is set on the tablet view It happens because on_barcode_scan doesn't check the product while searching the barcode. It would even be possible to set a lot not related to the product. Fix it by adding the product_id in the search Forward-Port-Of: odoo/enterprise#22444