Daily updates from Odoo
Navigate
Branch
Wednesday, June 22, 2022
16 changes
Enhancements to existing features
The Enterprise mobile interface now aligns with the standard Odoo web layout and uses the simplified mobile Kanban behavior introduced in the core product. This reduces duplication, improves consistency across editions, and keeps mobile navigation such as the control panel responsive during scrolling.
Original PR description
This PR is the followup of its' Community counterpart odoo/odoo#94134 where the WebClient layout has been standardized for both editions and the grouped Kanban implementation on mobile has been revamped. Part of the SCSS revamp task-2704984 task-2883057
The test setup for the enterprise messaging menu now uses the same web client and systray services as the real application instead of a special test-only helper. This improves test reliability and helps unblock related development work without changing the user experience.
Original PR description
The createMessagingMenu helper was used during tests to mount a messaging menu and test it. However, this approach is not very realistic and blocks some waiting PRs. In order to get closer from the reality, let's instanciate a webClient and a systrayService for the messagingMenu to be present at all time. community: https://github.com/odoo/odoo/pull/94301
This update removes outdated encoding comments from VoIP-related code files. It is an internal cleanup that keeps the codebase tidier without changing product behavior or user workflows.
Original PR description
Remove useless comments `# -*- coding: utf-8 -*-` from the VoIP codebase.
The reconciliation screen now keeps the relevant statement line filter visible when users arrive from the Journal Items list. This makes it easier for accounting teams to stay focused on the right transactions and complete reconciliation with less searching.
Original PR description
When coming from the Journal Items list, the reconciliation widget now shows the filter for the statement line.
Users with read-only access to a document workspace can now view documents without being offered actions they are not allowed to use, such as uploading, adding links, requesting documents, or using sidebar actions. The change also prevents unauthorized document moves between workspaces and shows a clear message when an action is not permitted, reducing confusion and protecting workspace permissions.
Original PR description
PURPOSE When a user has only read access to a workspace (when they have access through a 'readonly' group in the workspace settings), the top buttons (upload/add url/request/... see attachments) should be disabled. Feedback from task #2083596 SPECIFICATIONS If the user is on "read only" group : The only right that we have is to read the document. If we try to move a document to another workspace : DIsplay a Toaster LINKS PR #12351 Task-2086557
Planning screens and reports are easier to read and use, with allocated hours and percentages shown together and less empty space in planning cards. Users can now create repeating planning slots by day, week, month, or year, and templates can calculate an end hour based on the company's working calendar.
Original PR description
Purpose of this PR to improve generic UX of planning app. So, in this commit: - combine allocated hour and percentage column into allocated hour. - make `repeat_unit` selection field which is previously fixed for `week`. - add `end_hour` field which should be calculated based on the working calendar of the current company. task-2816515
Resolved issues and error corrections
Opening journal items from accounting reports now shows them grouped in the most relevant way by default. This makes it easier for users to review entries by account, journal, or partner depending on the report context.
Original PR description
By default when opening journal item view from report, group by accounts exception is for the following reports journal report: group by journal partner reports (partner ledger, aged receivable, payable): group by partner
Code cleanup and technical improvements
The manufacturing work order tablet flow was simplified by removing outdated action flags and keeping the PDF viewer behavior consistent. This reduces maintenance complexity while preserving the operator experience on the shop floor.
Miscellaneous changes
Currently, 'parent task' appears in group by in planning even if subtasks feature is disabled. In this PR, project.group_subtask_project group is entered on 'parent task' group by. So if subtasks feature is enabled then 'parent task' will appear. task-2884027 Forward-Port-Of: odoo/enterprise#28722 Forward-Port-Of: odoo/enterprise#28417
Original PR description
Currently, 'parent task' appears in group by in planning even if subtasks feature is disabled. In this PR, project.group_subtask_project group is entered on 'parent task' group by. So if subtasks feature is enabled then 'parent task' will appear. task-2884027 Forward-Port-Of: odoo/enterprise#28722 Forward-Port-Of: odoo/enterprise#28417
This reverts commit deee65a8f76c5dbddbd04fa11a331eb434e5dce9 as not applicable from version 15.0 and after. Forward-Port-Of: odoo/enterprise#28703 Forward-Port-Of: odoo/enterprise#28603
Original PR description
This reverts commit deee65a8f76c5dbddbd04fa11a331eb434e5dce9 as not applicable from version 15.0 and after. Forward-Port-Of: odoo/enterprise#28703 Forward-Port-Of: odoo/enterprise#28603
This is the follow up of https://github.com/odoo/enterprise/pull/26152 Taskid: 2855699 Forward-Port-Of: odoo/enterprise#28678 Forward-Port-Of: odoo/enterprise#28312
Original PR description
This is the follow up of https://github.com/odoo/enterprise/pull/26152 Taskid: 2855699 Forward-Port-Of: odoo/enterprise#28678 Forward-Port-Of: odoo/enterprise#28312
In PR https://github.com/odoo/enterprise/pull/28578 we did a little refactoring to support the new cfdi 40 and forgot to provide templates for the old methods as _l10n_mx_edi_get_invoice_templates was only implemented in l10n_mx_edi_40 and not in l10n_mx_edi. This avoids a traceback in v15.0 when not installing the new modules and sending invoices. (as it would not find back the method) Forward-Port-Of: odoo/enterprise#28643
Original PR description
In PR https://github.com/odoo/enterprise/pull/28578 we did a little refactoring to support the new cfdi 40 and forgot to provide templates for the old methods as _l10n_mx_edi_get_invoice_templates was only implemented in l10n_mx_edi_40 and not in l10n_mx_edi. This avoids a traceback in v15.0 when not installing the new modules and sending invoices. (as it would not find back the method) Forward-Port-Of: odoo/enterprise#28643
Steps to follow: - Make sure Mexican Localization is installed - Go to Accounting module > Reporting > Trial Balance (or Balance General) - Try collapsing the lines of the registers, the lines won't collapse opw-2869123 Forward-Port-Of: odoo/enterprise#28427
Original PR description
Steps to follow: - Make sure Mexican Localization is installed - Go to Accounting module > Reporting > Trial Balance (or Balance General) - Try collapsing the lines of the registers, the lines won't collapse opw-2869123 Forward-Port-Of: odoo/enterprise#28427
Forward-Port-Of: odoo/enterprise#27816
Original PR description
Forward-Port-Of: odoo/enterprise#27816
Forward-Port-Of: odoo/enterprise#28682 Forward-Port-Of: odoo/enterprise#28345
Original PR description
Forward-Port-Of: odoo/enterprise#28682 Forward-Port-Of: odoo/enterprise#28345
How to reproduce the bug ? - install quality - create a second company - in quality, create 2 quality teams, one for each company, with different email aliases - send an email to the address of the quality team of the created company What is the bug ? When one needs to create a quality alert from an email, there is an error if the quality team belongs to a company different from the "main" one. This is due to the fact that when we create an alert, we are trying to access its tea
Original PR description
How to reproduce the bug ? - install quality - create a second company - in quality, create 2 quality teams, one for each company, with different email aliases - send an email to the address of the quality team of the created company What is the bug ? When one needs to create a quality alert from an email, there is an error if the quality team belongs to a company different from the "main" one. This is due to the fact that when we create an alert, we are trying to access its team. opw-2781475 Signed-off-by: Adrien Minet <admi@odoo.com> Forward-Port-Of: odoo/enterprise#28380