Daily updates from Odoo
Navigate
Branch
Tuesday, July 12, 2022
17 changes
Enhancements to existing features
Several HR-related screens have been modernized to use Odoo’s newer interface framework. This should make appraisal, expense extraction, and referral kanban views more consistent, maintainable, and ready for future improvements without changing core business workflows.
Original PR description
*: hr_appraisal, hr_expense_extract, hr_referral task-2900536
This update improves daily workflows across Field Service, Helpdesk, Planning, and related reporting screens. Users get clearer search options, better default views, improved report navigation, and small layout refinements that make scheduling, ticket handling, and task management easier.
Original PR description
* helpdesk, helpdesk_sale, industry_fsm, industry_fsm_{report, sale}, planning, project_forecast, project_timesheet_forecast, sale_planning, snailmail_account_followup PURPOSE Generic improvements…
* helpdesk, helpdesk_sale, industry_fsm, industry_fsm_{report, sale},
planning, project_forecast, project_timesheet_forecast, sale_planning,
snailmail_account_followup
PURPOSE
Generic improvements for field services.
SPECIFICATION
In helpdesk,
- reporting > sla status analysis:
added the cohort view based on ticket creation and closing dates
and displayed the 'days to reach sla' measure by default
- helpdesk.team kanban card:
fixed o_kanban_card_content div position
- helpdesk.ticket search view:
remove the search on ticket id and include it into the search on ticket
remove the search on rating text
rename the search on 'ref. sales order' into 'sales order item'
add a quick search on SO
In planning,
- reporting > planning analysis:
added the calendar view
- schedule + my planning menus:
added the pivot and graph views
In field service,
- planning menus:
set default scale of the gantt view to 'week' (except in project menu)
switched the list and kanban views form place
moved the calendar view to the left of the pivot view
- project.project list view:
renamed 'default worksheet' into 'worksheet template'
- my tasks > tasks:
moved the list view to the right of the kanban view
- all tasks menus:
moved the map view to the right of the kanban view
In project,
- project > my tasks menu:
removed the group by > personal stage from the search view and
seted as default groupby for kanban view
- project.task form view:
moved the 'recurrent' field above the tag
- improvements in followup_send_wizard form view
TaskID-2731708My Timesheets now shows planned project and task rows for the selected period, helping employees see where they are expected to log time. The grid layout is also simplified by reducing unnecessary total rows and visual clutter, making timesheet entry easier to read and use.
Original PR description
… to planning - Link to planning In 'My Timesheets' grid view, display an empty row for the project/tasks on which the current user is supposed to be working during the period displayed according to the published planning.slot that were assigned to him. - Simplify grid sections Hide the totals line when there are sections and there is only 1 level of group by Do not highlight the 'add a line' row in grey Related PR: https://github.com/odoo/odoo/pull/93169 task-2859663
Users can now edit the filter criteria behind spreadsheet pivots directly from the Pivot Properties panel. This makes it easier to adjust which business data is included in a pivot report without recreating it or relying on technical workarounds.
When a SEPA direct debit payment provider is disabled, its linked payment tokens are now removed from related documents and archived. This prevents staff from accidentally using inactive payment methods and stops them from becoming active again later.
Original PR description
Before this commit, zombie payment tokens (= tokens linked to disabled acquirers) could still 1) be used by internal users and 2) reactivated when the acquirer’s state changed to ‘test’ or ‘enabled’. This is not desirable because zombie tokens should neither be used, nor reactivated. After this commit, all tokens related to an acquirer are unassigned from linked documents and archived as soon as the acquirer’s state is changed to ‘disabled’. Creating a payment with an archived token is prohibited. In addition, archived tokens cannot be un-archived anymore. task-2649806 See also: - https://github.com/odoo/odoo/pull/93774
When adding a budget from a project, the budget line now automatically uses the project's analytic account. This reduces manual entry and helps keep project budgeting aligned with the correct financial tracking.
Original PR description
Before this commit, when the user wants to add a budget from the project update of a project, the budget line added does not have the AA of the current project by default. This commit adds the AA of the project by default in the budget line when the user is in the dialog form view of Budget to add a new budget for the project. task-2861207
Resolved issues and error corrections
This change adds a missing configuration field needed by the French payroll module. It prevents installation failures in automated single-module builds, helping ensure the module can be deployed reliably.
Original PR description
The field `country_code` was not found in the view, hence it prevented the module from being installed in the single module build on the runbot.
This fixes an internal payroll accounting test so it matches the updated leave form behavior. The change helps keep Belgian payroll accounting checks reliable after the leave days field was made read-only.
Original PR description
As part of https://github.com/odoo/odoo/pull/95534, the number of days field for a hr.leave has been set as readonly. It also implies that number_of_days is no longer part of the form view to only keep number_of_days_display. This commit fixes the test using number_of_days by replacing it with number_of_days_display. task-2901951
Fixes an issue where rapidly typing in the Home Menu could drop some characters when opening the command palette. Users now get the full intended search text, making app search and navigation more reliable.
Original PR description
Before this commit, in the HomeMenu, typing several characters very quickly could result in some not being present in the command palette when it was opened. Exemple: In the HomeMenu,if I type "a" "b" "c" quickly the command palette will open with the search value "/a" or "/ac". So we have lost the second and/or third character. Why: All characters typed between the first and the moment the command pallet is not yet mounted are lost because the search bar of the command pallet is not yet available. Solution: If you use openPalette and the command palette is already open. The configuration of the command pallet will be overwritten by the one given to openPalette. In our case, we can pass new configurations with the correct searchValue until the command palette is returned. Task-ID: 2906623
Code cleanup and technical improvements
This update reorganizes rental sales files and menus to make the application easier to maintain without changing how users work. It also tidies view definitions and improves one error message translation, reducing future maintenance risk.
Original PR description
* Clean inconsistent xml indentation * correctly group xml/python code by models (in separate files) * use clear file names to easily know the xml content. * Use a dedicated file to specify all the application menus Note: files split are done in two commits to keep the blame history of the files.
Miscellaneous changes
Before this commit: Install documents In the aliases, in the alias_defaults, change the default tag_id, folder_id or create_share_id to one that does not exist (for example, for the default alias inbox, change from {'tag_ids': [(6, 0, [1])], 'folder_id': 1, 'partner_id': False, 'create_share_id': 2} to {'tag_ids': [(6, 0, [1000])], 'folder_id': 1, 'partner_id': False, 'create_share_id': 2}) Then, send a document to that alias. It will not find the relevant tag_id, folder_id or
Original PR description
Before this commit: Install documents In the aliases, in the alias_defaults, change the default tag_id, folder_id or create_share_id to one that does not exist (for example, for the default alias…
Before this commit:
Install documents
In the aliases, in the alias_defaults, change the default tag_id, folder_id or create_share_id to one that does not exist (for example, for the default alias inbox, change from
{'tag_ids': [(6, 0, [1])], 'folder_id': 1, 'partner_id': False, 'create_share_id': 2}
to {'tag_ids': [(6, 0, [1000])], 'folder_id': 1, 'partner_id': False, 'create_share_id': 2})
Then, send a document to that alias.
It will not find the relevant tag_id, folder_id or create_share_id and will send back an error without registering the document.
After this commit:
If a tag_id does not exist, remove it (documents.tag are not mandatory)
If a create_share_id does not exist, remove it (documents.share are not mandatory)
If a folder_id does not exist:
1. Use the folder of the first tag_id or
2. Use the folder of the create_share_id or
3. Use the first folder without documents.share, to avoid having important documents disclosed to a potentially public folder.
OPW 2786973
Forward-Port-Of: odoo/enterprise#29320The computation of the field schedule_count crashes when triggered on multiple records. Base PR of the feature: #20530 Forward-Port-Of: odoo/enterprise#29332
Original PR description
The computation of the field schedule_count crashes when triggered on multiple records. Base PR of the feature: #20530 Forward-Port-Of: odoo/enterprise#29332
Adapt web_studio unit test. During Editor initialization, we now detect if the editable element contain orphan inline nodes. If so we transform the base element HTML to put those orphans inside <p> containers. task-2877273 Forward-Port-Of: odoo/enterprise#29130 Forward-Port-Of: odoo/enterprise#28965
Original PR description
Adapt web_studio unit test. During Editor initialization, we now detect if the editable element contain orphan inline nodes. If so we transform the base element HTML to put those orphans inside <p> containers. task-2877273 Forward-Port-Of: odoo/enterprise#29130 Forward-Port-Of: odoo/enterprise#28965
Steps to reproduce: - Install Accounting - Go to accounting -> Reporting -> Executive Summary - Export to pdf Issue: When exporting the Executive Summary, the line 'Probability' and 'Balance Sheet' would not display properly on the pdf. Cause: An additional span would be added to replace the a of the original document. Meanwhile the rendered would miss-interpret those markup and change the design. Solution: Not replace the a by span as it doesn't change the result on the rende
Original PR description
Steps to reproduce: - Install Accounting - Go to accounting -> Reporting -> Executive Summary - Export to pdf Issue: When exporting the Executive Summary, the line 'Probability' and 'Balance Sheet' would not display properly on the pdf. Cause: An additional span would be added to replace the a of the original document. Meanwhile the rendered would miss-interpret those markup and change the design. Solution: Not replace the a by span as it doesn't change the result on the rendered pdf. opw-2878278 Forward-Port-Of: odoo/enterprise#28364
Before this commit, `upload a PDF to sign` button is missing in the sign >> documents and instead, it was showing the create button due to missing js_class on view in recent js refactoring So in this commit, added the js_class to replace the 'create' button with `upload a PDF to sign`. task-2887200 Forward-Port-Of: odoo/enterprise#29155
Original PR description
Before this commit, `upload a PDF to sign` button is missing in the sign >> documents and instead, it was showing the create button due to missing js_class on view in recent js refactoring So in this commit, added the js_class to replace the 'create' button with `upload a PDF to sign`. task-2887200 Forward-Port-Of: odoo/enterprise#29155
If applied, this commit will fix an error caused by this pr: https://github.com/odoo/enterprise/pull/27621 Steps to reproduce: 1- install l10n_mx_edi 2- you get a traceback error Bug: in https://github.com/odoo/enterprise/pull/27621 the field l10n_mx_edi_locality is added in l10n_mx_edi's override of _formatting_address_fields, however, in v14 this field was moved to l10n_mx_edi_extended Fix: Seperate the overriding over both modules with the corresponding fields OPW-28
Original PR description
If applied, this commit will fix an error caused by this pr: https://github.com/odoo/enterprise/pull/27621 Steps to reproduce: 1- install l10n_mx_edi 2- you get a traceback error Bug: in https://github.com/odoo/enterprise/pull/27621 the field l10n_mx_edi_locality is added in l10n_mx_edi's override of _formatting_address_fields, however, in v14 this field was moved to l10n_mx_edi_extended Fix: Seperate the overriding over both modules with the corresponding fields OPW-2896136 Forward-Port-Of: odoo/enterprise#29102 Forward-Port-Of: odoo/enterprise#28915
Since 15.0, the SignItemNavigator was not correctly opening signature wizards for sign items added while signing. This occurs because the html structure between previously added sign items and sign items added while signing are different. Therefore the SignItemNavigator was triggering the click on the wrong element. This commit fixes this issue. task-2783947 Forward-Port-Of: odoo/enterprise#25352
Original PR description
Since 15.0, the SignItemNavigator was not correctly opening signature wizards for sign items added while signing. This occurs because the html structure between previously added sign items and sign items added while signing are different. Therefore the SignItemNavigator was triggering the click on the wrong element. This commit fixes this issue. task-2783947 Forward-Port-Of: odoo/enterprise#25352