Daily updates from Odoo
Friday, September 2, 2016
34 changes · master
New functionality added to Odoo
Adds support for Ecuador's ATS tax declaration reporting required by the SRI. This helps Ecuadorian businesses capture retention invoices, tax codes, identification data, and related reference tables needed for local compliance reporting.
Original PR description
Description of the issue/feature this PR addresses: ATS Tax Declaration in Ecuador ( http://www.sri.gob.ec/de/172 ) 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
A new module category was added to organize GitHub-related integration connectors alongside Discuss-style modules. This helps users and administrators find and manage these connector modules more easily as the integration area expands.
Original PR description
[ADD]: added a new module for connectors(list of all discuss type module). Task: https://www.odoo.com/web?#id=19545&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.rMlx5SNEK1Dm59pP
This update adds a new option to use sales quotations or orders during bank statement reconciliation. It helps businesses connect incoming payments to the right sales documents more accurately and streamlines the reconciliation workflow.
This change lets users use sales quotations or orders while reconciling bank statement transactions, making it easier to connect incoming payments to the right customer activity. It also improves the reconciliation screen and navigation so the process is more flexible and smoother for users.
This change adds more automated checks around bank reconciliation, including multi-currency scenarios. It helps reduce the risk of accounting issues reaching users by catching problems earlier during development.
Adds barcode-based workflows for manufacturing orders and work orders. This helps shop floor teams process production steps faster, reduce manual entry, and improve traceability in manufacturing operations.
Enhancements to existing features
This update removes unnecessary code evaluation in the stock product logic, making the implementation simpler and slightly more efficient. It also includes an administrative CLA update for a contributor, with no expected change for everyday users.
Original PR description
**Description of the issue/feature this PR addresses:** Improves code quality and performance **Current behavior before PR:** eval + 2 explicit casts **Desired behavior after PR is merged:** code clean and good perfs ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Because in this file eval is unnecessary.
This change simplifies the company profile by moving configuration options into each relevant app's Settings area. Business users get a clearer setup experience, with company-specific options still supported but managed from a more consistent location.
Original PR description
Task : https://www.odoo.com/web?#id=27812&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.ea3a82ad157ba392f03749b25c4e19ad 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 no custom form is defined, Odoo now creates a fuller default form that includes relationship fields previously left out. Large content areas such as long text, HTML, and related-record lists also use the available page width, making training and data review easier.
Original PR description
Theses changes are useful for training when we define model before teaching the views. 1. When a model has no form defined, a default view is generated displaying all fields of the model. The one2many and many2many fields were not displayed on the form, probably for aesthetic or historical (2008) reasons. 2. one2many, many2many, text and html fields should take all space in a form view for a better rendering instead of taking only 2 col or not having the label in front the field. **To merge in 9.0: vote :tada: To merge in master: vote :heart:** Before:  Now: 
Warehouse users now receive a warning when processing a transfer that involves different source or destination locations. This helps prevent accidental stock movements and gives teams a chance to review location details before completing the operation.
Original PR description
task: https://www.odoo.com/web#id=12365&view_type=form&model=project.task&action=333&active_id=131 pad: https://pad.odoo.com/p/r.VfA7AkfvkykGUKCn
The website quotation feature has been migrated to Odoo's newer internal framework. This should make the feature easier to maintain and reduce duplicated or outdated backend elements without changing the core customer-facing quoting workflow.
Original PR description
task: https://www.odoo.com/web#id=12132&view_type=form&model=project.task&action=327&menu_id=5200 pad: https://pad.odoo.com/p/r.19581cae2884b8b309d2b3153792a804 ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Budget reports have been updated to work with the newer reporting approach and to run more efficiently. This should make budget analysis smoother for users while removing outdated report code that is no longer needed.
Original PR description
Description of the issue/feature this PR addresses: Task: https://www.odoo.com/web#id=22216&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.d359debbc0ebab15039fe55e6065cc47 ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The event sales module was updated to use Odoo's newer internal framework, helping keep the feature easier to maintain and compatible with ongoing platform improvements. This mainly affects how event-related products, sales orders, registrations, and demo data are handled behind the scenes, with limited direct change for everyday users.
Original PR description
...py) to new API - Task: https://www.odoo.com/web#id=12010&view_type=form&model=project.task&action=333&active_id=131 - Pad: https://pad.odoo.com/p/r.Hddf0qvcf9AJY1fL
Survey date questions now use improved date widgets, making it easier and more reliable for respondents to enter dates. This improves the survey-taking experience and helps businesses collect cleaner date-based responses.
Original PR description
Task: https://www.odoo.com/web#id=22615&view_type=form&model=project.task&action=327&menu_id=4720 Pad: https://pad.odoo.com/p/r.a8df8088c9902d4aebedb95b6a9338fd
This update removes unnecessary automatic updates to fields that already come from their parent records, especially in accounting entries and expense flows. It reduces extra database work when creating or changing records, improving performance while keeping the same business behavior.
Original PR description
The field journal_id and date are both required on account.move and are stored related on account.move.line. Setting the required on the account.move.line allows to make it required in the views or for the ORM but in practice it will be same as it's required on the parent. Making it required is a performance killer as it forces to specify a value for the create which will retrigger an update on the parent move. This means that adding a line with a date value on an account.move with already 10 lines will trigger 11 updates (date of the new line -> date of the move -> date on the 10 existing lines), even if the value has not changed.
This update standardizes wording in the payment area to make labels or messages clearer and more consistent. It is a small usability improvement that helps reduce confusion for users working with payment configuration or flows.
Original PR description
@dbo-odoo check this.
This update improves the Project app experience by simplifying task reporting, removing a problematic cumulative flow report, and making project cards and onboarding data clearer. It also adds a clearer message for Pad configuration, reducing confusion for users and avoiding errors when editing project stages or deleting columns.
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
Company-specific configuration options have been relocated from the company form into the settings areas of their related apps. This simplifies company records and makes it easier for users to find and manage configuration in one consistent place.
Original PR description
Task: https://www.odoo.com/web?#id=27812&view_type=form&model=project.task&menu_id=4720 Pad: https://pad.odoo.com/p/r.ea3a82ad157ba392f03749b25c4e19ad
Resolved issues and error corrections
This update corrects how many Odoo modules label their built-in menus, groups, and related records so they belong to the module that actually provides them. This helps ensure module uninstallations clean up properly and translations are available when languages are installed before optional modules.
Original PR description
Several modules defines records with the external ID `base.foo_bar` while it is created inside this module (typically menus and groups). While there is no technical reasons to do so but this may…
Several modules defines records with the external ID `base.foo_bar` while it is created inside this module (typically menus and groups). While there is no technical reasons to do so but this may introduce issues: - these records will not be deleted during uninstall - if a language is loaded before the installation of the module, it won't be translated The uninstallation will only remove the records with an external id linked to this module (these would only be removed when removing base). Installing a language before the module will drop the translations not linked to an existing external id (as it can not be resolved). Just to make @KangOl life easier: - menu_action_currency_form -> account & sales_teams (2 menus) - menu_association -> membership - menu_event_config-> membership - menu_import_crm -> crm - group_hr_user -> hr - group_hr_manager -> hr - group_hr_attendance -> hr (shouldn't it be moved to hr_attendance btw?) - group_hr_attendance_use_pin -> hr_attendance - action_partner_mass_mail -> mail (why is it duplicated?) - group_equipment_manager -> maintenance - menu_association -> membership - menu_marketing_config_association -> membership - menu_mrp_config -> mrp - menu_mrp_root -> mrp - menu_main_pm -> project - menu_project_config_project -> project - menu_project_report -> project - menu_project_general_settings -> project - menu_purchase_root -> purchase - purchase_report -> purchase - menu_aftersale -> sale_stock - menu_invoiced -> sale_stock - menu_action_res_partner_bank_form -> sales_team - menu_sale_report -> sales_teams - sales_team_config -> sales_teams - group_survey_user -> survey - group_survey_manager -> survey - group_website_publisher -> website - group_website_designer -> website - module_category_theme_hidden -> website_theme_install (does it impact theme modules?)
This fixes an issue where boolean fields written as text, such as "False" or "0", could be incorrectly treated as true during XML data loading. The change helps ensure imported or demo records reflect the intended active/inactive or yes/no settings.
Original PR description
Description of the issue/feature this PR addresses:
Process boolean value where is used without a eval
e.g.
``` xml
<?xml version='1.0' encoding='UTF-8'?>
<odoo>
<record id="res_partner_demo_01" model="res.partner">
<field name="name">Test demo 01</field>
<field name="active">False</field>
<field name="supplier">0</field>
<field name="customer" eval="False"/>
</record>
</odoo>
```
Current behaviour before PR:
`<field name="active">False</field>` Processed like as a `True`
`<field name="supplier">0</field>` Processed like as a `True`
`<field name="customer" eval="False"/>` Processed like as a `False`
Desired behaviour after PR is merged:
`<field name="active">False</field>` Processed like as a `False`
`<field name="supplier">0</field>` Processed like as a `False`
`<field name="customer" eval="False"/>` Processed like as a `False`Cancelling a product return now correctly restores the link to the next warehouse movement. This helps keep inventory operations consistent and prevents follow-up transfers from being left unassigned.
Original PR description
Task : https://www.odoo.com/web#id=12762&view_type=form&model=project.task&menu_id=3942&action=327 Pad : https://pad.odoo.com/p/r.rLOfjEuqxD2A0f8B
Customers will no longer receive the internal notification that their quotation was viewed. The notification is now treated as an internal note, so only relevant salespeople following the document are informed.
Original PR description
Description of the issue/feature this PR addresses: - "Quotation viewed" notification should not be received by customer Task:https://www.odoo.com/web#id=26662&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad:https://pad.odoo.com/p/r.f4e9d33a8dac45aed936a6708704a391 Current behavior before PR: - This notification "Quotation viewed by customer" is received by the customer. Desired behavior after PR is merged: - This notification "Quotation viewed by customer" shouldn't be received by the customer and only the salesman who follow the notes will get it. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix moves the product purchasing option back to the core Product app so it is available where other apps, such as Accounting, expect it. This prevents missing-setting issues for businesses that use product and accounting features without installing Purchase.
Original PR description
The 'purchase_ok' field has been moved into the 'purchase' module in rev https://github.com/odoo/odoo/commit/e945b86d5a61e53a9104ab6cc4ed4a1c060587e4 and removed from 'product' module in rev https://github.com/odoo/odoo/commit/fee03009cfcc41d108a79a2380912f21bc825d77 to fix a duplicated field. But it should actually stay only in 'product' module because the field is needed in the 'account' module which doesn't depend of 'purchase'. So to fix it we set back the 'purchase_ok' field in the product module as it was originally in the rev https://github.com/odoo/odoo/commit/e23e018285b17450af97cf93165704926f8248db
This update corrects records that were incorrectly registered as belonging to the core Base app instead of the app that created them. This helps ensure apps uninstall cleanly and translations are kept when languages are installed before those apps.
Original PR description
cf odoo/odoo#12812 Several modules defines records with the external ID `base.foo_bar` while it is created inside this module (typically menus and groups). While there is no technical reasons to do so but this may introduce issues: - these records will not be deleted during uninstall - if a language is loaded before the installation of the module, it won't be translated The uninstallation will only remove the records with an external id linked to this module (these would only be removed when removing base). Installing a language before the module will drop the translations not linked to an existing external id (as it can not be resolved).
Code cleanup and technical improvements
This change updates the system’s internal framework name from “openerp” to “odoo” across the codebase. It helps keep the product’s technical foundation aligned with the Odoo brand while preserving existing business functionality.
Original PR description
- Rename the module - Adapt imports in the framework - Adapt import hooks
The website recruitment app has been migrated to Odoo's newer application framework. This helps keep the hiring website functionality maintainable and aligned with current platform standards, with no major change expected for end users.
Original PR description
Task : https://www.odoo.com/web/#id=12028&view_type=form&model=project.task&menu_id=3942&action=327 Pad : https://pad.odoo.com/p/r.CFZ51hLERFpk5s06
The Project app has been updated to Odoo's newer internal framework and reorganized for easier maintenance. Some outdated and already-removed capabilities were cleaned out, helping keep the app more stable and easier to improve over time.
The account budgeting module was migrated to Odoo's newer internal framework and its files were reorganized. This should make the budgeting feature easier to maintain and test, while preserving the existing business functionality for users.
Original PR description
Task: https://www.odoo.com/web?#id=12160&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.3425f60cbab97845a13fcc165ff3657d
The gamification app was updated to use Odoo's newer internal framework, making it easier to maintain and test. Some outdated screens and tools tied to removed website behavior were also cleaned up, reducing complexity without introducing a new business feature.
Original PR description
- Task : https://www.odoo.com/web#id=13555&view_type=form&model=project.task&action=327&menu_id=4720 - Pad : https://pad.odoo.com/p/r.274053bc777a74f558fab443b8f1089f
The CRM partner assignment module was updated to Odoo's newer internal framework while keeping its business purpose intact. This should make the module easier to maintain and more reliable for future improvements, with minimal direct impact on everyday users.
Original PR description
Task: https://www.odoo.com/web#id=12139&view_type=form&model=project.task&action=327 Pad: https://pad.odoo.com/p/r.fPuJnMpZkc0rcB75
The Gengo translation module was reorganized and migrated to Odoo's newer internal framework. This helps keep the translation integration maintainable and aligned with current platform standards, with limited expected impact on day-to-day users.
Original PR description
Task: https://www.odoo.com/web#id=12209&view_type=form&model=project.task&menu_id=3942&action=327 Pad: https://pad.odoo.com/p/r.4YJMn6R8itJDcfnQ
This update removes legacy workflow definitions across several Odoo apps and replaces them with direct Python logic. For businesses, this keeps existing processes working while making the system easier to maintain and less dependent on outdated internal mechanisms.
Original PR description
Remove all workflows and replace by python code. odoo tasks (1 per model with workflow, 8 total): https://www.odoo.com/web#id=27198&view_type=form&model=project.task&action=333&active_id=248&menu_id=5195 https://www.odoo.com/web#id=27200&view_type=form&model=project.task&action=333&active_id=248&menu_id=5195 https://www.odoo.com/web#id=27205&view_type=form&model=project.task&action=333&active_id=248&menu_id=5195 https://www.odoo.com/web#id=27871&view_type=form&model=project.task&action=333&active_id=248&menu_id=5195 https://www.odoo.com/web#id=27201&view_type=form&model=project.task&action=333&active_id=248&menu_id=5195 https://www.odoo.com/web#id=27199&view_type=form&model=project.task&action=333&active_id=248&menu_id=5195 https://www.odoo.com/web#id=27207&view_type=form&model=project.task&action=333&active_id=248&menu_id=5195 https://www.odoo.com/web#id=27202&view_type=form&model=project.task&action=333&active_id=248&menu_id=5195
The point of sale loyalty module has been reorganized and migrated to Odoo's newer application framework. This keeps loyalty features maintainable and aligned with current platform standards without introducing a major functional change for users.
Original PR description
Task: https://www.odoo.com/web#id=13731&view_type=form&model=project.task&action=327 Pad: https://pad.odoo.com/p/r.NmkjQTXj345Cnydy
This update aligns several business flows with recent platform changes by removing outdated workflow calls. It helps keep sales, purchasing, accounting, subscriptions, and portal-related processes compatible and reduces the risk of errors from obsolete automation hooks.
Original PR description
- adaptation to removal of workflows in community modules. (PR: https://github.com/odoo/odoo/pull/13103 ) - correction of already removed workflow calls. (purchase.order, sale.order)