Daily updates from Odoo
Navigate
Branch
Wednesday, July 12, 2023
19 changes
New functionality added to Odoo
Accounting users can now automatically reconcile journal entries by entering criteria in a dedicated wizard. This reduces manual matching work and helps accounting teams close or clean up entries more efficiently.
Original PR description
Adds the possibility to auto-reconcile Journal Entries, given certain parameters to be filled in the wizard. task-3340093
Enhancements to existing features
Helpdesk users can no longer create ticket stages from views that are not tied to a specific team. This prevents newly created stages from disappearing after refresh and avoids confusion caused by stages that are not visible in team pipelines or cross-team views.
Original PR description
Purpose: prevent the creation of stages when not viewing the tickets of a specific team. Otherwise, that stage will end up in a sort of limbo: it is not displayed in teams pipelines because it has none set, and it is not visible in cross-teams views if it doesn't have any tickets. In addition, it can be confusing for users if their newly created stage disappears at the first refresh of the page. Implementation: fixed by overriding the canCreateGroup in the HelpdeskTicketRenderer, the context of the list now needs an active_id, only available from the Helpdesk Team actions Task-3277199 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Bank and cash statement tools are easier to access and manage directly from the bank reconciliation kanban view. The journal dashboard is improved for bank and cash journals, while the older bank reconciliation report is removed to streamline the workflow.
Original PR description
In the process of making bank statements optional, many features relating to statements were lost. This PR serves to improve the usability of bank statements. It provides the ability to view and manage them directly on the kanban view of the bank reconciliation widget. Also, improve the journal dashboard kanban for bank/cash journals Remove the bank reconciliation report. Task-3270046
The project creation wizard now starts with Billable turned off, making onboarding less complex for users creating new projects. The partner/customer field also includes clearer guidance, and the Billable and Timesheets options have been rearranged for a more intuitive setup flow.
Original PR description
Before this commit when creating new project then in wizard form Billable is by default checked and no placeholder is given for partner field in Billable. This commit focuses on improvement in create project wizard by removing checked by default from Billable so that user get simplified and less complex view of tasks during the onboarding. Added a placeholder for partner field which help user to understand the purpose of field and switched the position of Billable and Timesheets. change test case according to new changes. task-3377998
Tasks that are not attached to a specific project can now use the same business features as regular project tasks, including timesheets, billing, materials, worksheets, dependencies, milestones, and quotations. This makes task management more consistent across project, field service, documents, and timesheet workflows, reducing limitations for teams that work with standalone tasks.
Original PR description
_*: project_enteprise timesheet_grid industry_fsm industry_fsm_sale industry_fsm_report - store project_root_id - allow all project features: allow_timesheets allow_billable allow_material allow_worksheets allow_task_dependencies allow_milestones allow_quotations Related: https://github.com/odoo/odoo/pull/125936 task-3367246
This update removes leftover references to old messaging widgets across several Odoo business modules. It has little direct impact on daily users, but keeps the system cleaner and avoids giving developers outdated examples to copy.
Original PR description
They have been removed in https://github.com/odoo/odoo/commit/3fea5b213, these must be left overs. They don't really do any harm besides providing a bad example for devs. Odoo PR: https://github.com/odoo/odoo/pull/127767
This update reorganizes where a live chat helpdesk mail shortcut is defined, moving it into the mail area where it more naturally belongs. The change helps keep related functionality grouped together, reducing maintenance complexity without changing day-to-day user workflows.
Original PR description
community: https://github.com/odoo/odoo/pull/128120
Resolved issues and error corrections
Invoice reports for Chilean and Mexican electronic invoicing now show international trade terms correctly after an upstream layout change. The Chilean invoice also removes a duplicate trade term from the bottom section, making the document clearer for users and customers.
Original PR description
In those EDI some xpath were broken due to change in the community pr (https://github.com/odoo/odoo/pull/118954). For l10n_mx, changing the xpath was enough. For l10n_cl the xpath is useless since the information of incoterm in repeated twice (header and bottom) and we decided to remove it from the bottom of the invoice task: 3273460
The update makes internal holiday-related tests less dependent on preset demo company data. This helps prevent test failures caused by unrelated demo data changes, improving reliability for ongoing development.
Original PR description
Before this commit, the hr_holiday tests used base_company to setup the tests. This resulted in the tests interacting with the demo data that were linked to this company, eg stress days. With this commit, the tests are now independent of this data, and will therefore not be affected by any changes to it.
Features or functions removed from Odoo
An obsolete VoIP call transfer action was removed because call transfers are now handled directly in the browser interface. This is a low-impact cleanup that reduces unused code without changing the expected user experience.
Original PR description
This action is no longer used because it is directly triggered in javascript. task-3416597
Code cleanup and technical improvements
This update reorganizes parts of Odoo Studio's editor interface and prepares the XML resource editor to support report editing. It improves how related resources are displayed and managed, making future report customization work clearer and easier to build on.
The Peruvian accounting reports have been reorganized by merging the PLE books functionality into the main Peru reports module. This simplifies maintenance and keeps related compliance reporting features in one place without changing the business purpose of the reports.
Miscellaneous changes
Check if the field is present in the sale order and it's not False before using it, to ensure that "website_sale" is installed. For more information, please check: https://github.com/odoo/enterprise/pull/43368/commits/76c4500e32c0b7326d369e829c8708a573c6723f Forward-Port-Of: odoo/enterprise#43812
Original PR description
Check if the field is present in the sale order and it's not False before using it, to ensure that "website_sale" is installed. For more information, please check: https://github.com/odoo/enterprise/pull/43368/commits/76c4500e32c0b7326d369e829c8708a573c6723f Forward-Port-Of: odoo/enterprise#43812
**Summary**: issue occurring on Helpdesk ticket merge. on method _update_foreign_keys. Custom column name with uppercase characters attempts to be matched to lower case column name resulting in ERROR: column "lower_cased_column" does not exist **Cause**: created identifier with double quotes, leading to creation of column name in the original case. Postgresql requires mixed case identifiers to use double quotation marks create, query, or manage PostgreSQL database object.
Original PR description
**Summary**: issue occurring on Helpdesk ticket merge. on method _update_foreign_keys. Custom column name with uppercase characters attempts to be matched to lower case column name resulting in ERROR: column "lower_cased_column" does not exist **Cause**: created identifier with double quotes, leading to creation of column name in the original case. Postgresql requires mixed case identifiers to use double quotation marks create, query, or manage PostgreSQL database object. **Solution**: alter this query to allow for mixed case identifiers to be matched. Additional queries on _update_foreign_keys method updated opw-3335628 Forward-Port-Of: odoo/enterprise#43217
The module mrp_accountant explicitly inherits methods and a view from stock_accountant but is not directly dependant on it. The dependency is implicit by the auto_install of stock_accountant and the shared dependencies the modules have. However the auto_install can be bypassed by users post installation. The dependency should be explicit. Forward-Port-Of: odoo/enterprise#43622
Original PR description
The module mrp_accountant explicitly inherits methods and a view from stock_accountant but is not directly dependant on it. The dependency is implicit by the auto_install of stock_accountant and the shared dependencies the modules have. However the auto_install can be bypassed by users post installation. The dependency should be explicit. Forward-Port-Of: odoo/enterprise#43622
Steps: Go to Timesheet > list view. Type "Mitchell" in the search bar, just as you would do if you were looking for its timesheets. Press enter. Issue: Well, now the view is filtered, but you just started a timesheet. Cause: We listen to key-down events, and if "enter", a timer starts. Before hand, we have a check, to only do it when no record is in edition. Yet, it doesn't cover this case. Fix: Add the condition that the event doesn't target an input or a text area. task-3413
Original PR description
Steps: Go to Timesheet > list view. Type "Mitchell" in the search bar, just as you would do if you were looking for its timesheets. Press enter. Issue: Well, now the view is filtered, but you just started a timesheet. Cause: We listen to key-down events, and if "enter", a timer starts. Before hand, we have a check, to only do it when no record is in edition. Yet, it doesn't cover this case. Fix: Add the condition that the event doesn't target an input or a text area. task-3413333 Forward-Port-Of: odoo/enterprise#43699
Adds a test for the related commit in Community, which does the following: Improves the update of accounting report expression when switching the engine to 'tax_tags'. To reproduce: 1) Create a new report line in a report with an expression using the 'external' engine, giving it "dudu" as formula. 2) Save your changes. 3) Modify your expression to use 'tax_tags' instead of 'external'. Save your changes. => +dudu and -dudu tax tags are now created (with this commit), as expected task :
Original PR description
Adds a test for the related commit in Community, which does the following: Improves the update of accounting report expression when switching the engine to 'tax_tags'. To reproduce: 1) Create a new report line in a report with an expression using the 'external' engine, giving it "dudu" as formula. 2) Save your changes. 3) Modify your expression to use 'tax_tags' instead of 'external'. Save your changes. => +dudu and -dudu tax tags are now created (with this commit), as expected task : 3270506 Forward-Port-Of: odoo/enterprise#43896 Forward-Port-Of: odoo/enterprise#43626
- Allow to duplicate an appointment resource - Display a selection element for resource when we don't display the avatar to select a resource. - Fix an issue where the encodeURI was leading to an error when going back in the process and selecting a new time slot. task-3357113 Forward-Port-Of: odoo/enterprise#43417
Original PR description
- Allow to duplicate an appointment resource - Display a selection element for resource when we don't display the avatar to select a resource. - Fix an issue where the encodeURI was leading to an error when going back in the process and selecting a new time slot. task-3357113 Forward-Port-Of: odoo/enterprise#43417
[FIX] account_report: load more functionality The issue: When attempting to load additional records by clicking on 'load more...', we encounter a traceback. This occurs because, during the initial report load, the option next_progress is sent as a JSON string instead of a dictionary (or JSON object). Consequently, when accessing this object in the _get_aml_line function at line 612, a traceback is raised due to its string format. Upon addressing this traceback, a new issue arises where the li
Original PR description
[FIX] account_report: load more functionality The issue: When attempting to load additional records by clicking on 'load more...', we encounter a traceback. This occurs because, during the initial report load, the option next_progress is sent as a JSON string instead of a dictionary (or JSON object). Consequently, when accessing this object in the _get_aml_line function at line 612, a traceback is raised due to its string format. Upon addressing this traceback, a new issue arises where the lines are correctly received from the backend but do not appear in the UI. This issue stems from the visibility of these lines not being updated, resulting in their absence from the user interface. The fix: - Sending the next_progress as a dictionary - updating the visibility of the loaded lines opw-3379697 Forward-Port-Of: odoo/enterprise#43216