Daily updates from Odoo
Thursday, June 9, 2016
7 changes
Enhancements to existing features
This change moves sales team permissions and related settings into the dedicated Sales Team area instead of spreading them across other apps. It improves consistency for teams using CRM, Sales, subscriptions, VoIP, and related workflows, while tightening which sales records users can see based on their team role.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now choose source and destination locations more freely when editing stock transfer operation details. This helps advanced warehouse flows, such as pick-pack-ship transfers, adjust locations across warehouses without being blocked by overly restrictive location rules.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr When doing an internal trasnfer, you can choose any destination location in the header, but not on the line This is problematic when doing a pick-pack-ship transfer. For the pick move, you may want to change the source destination location (maybe another warehouse why not) but as the transfer is already validated you cannot modify it on the form. But with the Operation Details (Pencil button) you can modify the source/destination location. The only problem is that a domain is forcing the user to choose a source destination that is a child of the source destination on the transfer, which makes impossible to choose a destination on another warehouse. This tool is pretty much advanced, so we don't need to be so restrictive.
This update lets developers use the WDB debugging tool when working on Odoo. It is an internal productivity improvement that can help technical teams investigate issues more efficiently, with no direct change for end users.
Original PR description
Description of the issue/feature this PR addresses: Allows the developer to use [wdb](https://github.com/Kozea/wdb/) as a debugger. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr https://github.com/odoo/odoo/pull/10710 @Tecnativa
This update enhances the CRM claims workflow with better claim forms, follow-up tracking, calendar access, and document-related actions. It helps teams manage customer issues more consistently and improves access to related communications and files.
Original PR description
Task: https://www.odoo.com/web#id=9372&view_type=form&model=project.task&menu_id=3942&action=327 Pad: https://pad.odoo.com/p/r.jhh4fJAi0f6GvlJ8
The barcode app has been reorganized and moved to Odoo's newer framework, making it easier to maintain and extend. Barcode rules and naming logic are now separated more clearly, which supports smoother updates for inventory, point of sale, and related barcode workflows.
Original PR description
Task: https://www.odoo.com/web#id=13727&view_type=form&model=project.task&menu_id=3942&action=327 Pad: https://pad.odoo.com/p/r.Sk6EXxq1CMJFBFwH
The Manufacturing app has been reorganized and updated to follow the newer Odoo development framework. This improves maintainability and test coverage without introducing major functional changes for end users.
Sales-related access rights and settings are now grouped under the sales team module instead of being spread across base and product areas. This makes module installation more intentional and ensures related apps such as CRM, VoIP, and subscriptions get the sales permissions they need when installed.
Original PR description
Purpose: Having the res_group defined in base and sales_team auto installed with mail doens't make sense. - Move the empty res_config class and the related view from base_setup to sales_team (base_setup only contains the 'General Settings' model and views - Move the 'sale' related content from product to sale module (Access rights, menuitems,...) - Set sales_team at autoinstall False. The module is installed when needed by crm or sale for example - Set sales_team as a dependency of voip. (Access rights defined for configuration purpose) - Set sales_team ad a dependency of subscription (Access rights issue too) Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes sales_team.group_sale_manager.