Daily updates from Odoo
Wednesday, January 24, 2024
10 changes
2 changes
Enhancements to existing features
Approval users can now filter requests by Approved, Refused, or Canceled status and group request lists by status or category. This makes it faster to review approval workloads, spot outcomes, and organize requests for follow-up.
Original PR description
- Add status filters 'Approved', 'Refused', and 'Canceled' - Add status group-by option Task: 3631957
The planning role search no longer shows role avatars when no matching result is found. This reduces visual clutter and makes the helper message in the search experience easier to read.
Original PR description
In this commit, we remove the role avatars shown when searching for a role in the search bar of the planning role menu and no result is found. The rationale is that the role avatars displayed in such cases are clashing visually with the textual action helper. task-3696673
8 changes
Enhancements to existing features
This update improves the spreadsheet pivot table functionality by cleaning up internal method names for better clarity, fixing date formatting issues in pivot headers, and enabling sorting of month headers. These changes enhance the user experience when working with pivot tables in spreadsheets by ensuring dates display correctly and providing better sorting capabilities.
The self-order kiosk system now has the ability to print kitchen tickets directly. This improvement streamlines the order workflow by enabling automatic ticket printing at the kiosk, reducing manual steps and improving kitchen communication for self-service ordering operations.
Original PR description
With this commit the kiosk will now print the kitchen tickets. Task: 3553947
This update streamlines the Hong Kong payroll module's demo data by removing unnecessary function calls and improving data accuracy. The changes fix leap year handling in payslip dates and prevent leave schedules from overlapping with weekends, making the demo data more realistic and easier to maintain.
Original PR description
Impacted Version: - 16.0 and above This commit improve below features: - Simplify demo data and remove unnessary function call - Improve demo_payslip_2 date_to for leap year - Improve leaves to avoid overlapping weekend X-original-commit: 45321a2 Forward-Port-Of: odoo/enterprise#54283
P&L reports that group by analytic accounts or plans are now significantly faster. The update adds a database index to the temporary table used for analytic reporting, reducing report generation time by up to 90% (from 21 seconds to 2.1 seconds for large datasets). This improvement makes financial reporting more responsive for users working with detailed analytic data.
Original PR description
## Description Opening a P&L report and doing some grouping by an analytic account or an analytic plan can be extremely slow. This is due to the fact that, in the goal of reusing the generic report…
## Description Opening a P&L report and doing some grouping by an analytic account or an analytic plan can be extremely slow. This is due to the fact that, in the goal of reusing the generic report engine, which is based on `account.move.line`, a temporary table is created that shadows said table, but overwrite the data with content from `account.analytic.line` instead. The temporary table has absolutely no indexes, therefor forcing a Seq.Scan for all queries done on the table. As the `account.analytic.line` model can grow quite large in general, sequential scans on that table quickly becomes slow. ## Fix We introduce 1 composite index on the temporary table to speed up the subsequent queries on it. This slows down the initial creation of the temporary table, at the benefit of significantly speeding up all report sections queries, which are done for each `account_type`. Since the temporary table has no traffic on it, the exclusive lock on the table for the index creation is immediately acquired, so the time taken to build the index is proportional to the size of the table. The index is dropped when the temporary table is dropped. ## Benchmark Durations of the request `get_report_informations` for a P&L report of the last fiscal year, all journals, and grouping by 1 analytic plan of a database with a bit above 200k AAL: | AAL Volume | Before | After | |------------|--------|-------| | 50k | 4.75s | 1s | | 100k | 9s | 1.4s | | 200k | 21s | 2.1s | (in the last line, the 2.1s -> 1.2s is for the index creation + analyze) Scaling is also better when it comes to grouping by more analytic accounts or plans. ## Reference opw-3659497 Community PR: https://github.com/odoo/odoo/pull/148490 Forward-Port-Of: odoo/enterprise#53817
The self-order kiosk system now has the ability to print kitchen tickets directly. This improvement enables kiosks to send orders to the kitchen printer, streamlining the order fulfillment process and reducing manual steps in self-service ordering workflows.
Original PR description
With this commit the kiosk will now print the kitchen tickets. Task: 3553947 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
This update improves the quality assurance of the payment system by expanding unit test coverage for payment provider and payment method functionality. By adding more comprehensive tests, the team can catch potential issues earlier and ensure the payment system works reliably across different scenarios.
Original PR description
Some logic of the `payment.provider` and `provider.method` models was not properly covered by unit tests. See also: - https://github.com/odoo/enterprise/pull/54930
This update enables website menu editing functionality on mobile devices by making the edit buttons visible. Previously, these buttons were hidden on mobile, preventing users from accessing menu customization features. With recent technical improvements to the menu system, editing now works seamlessly on mobile devices.
Original PR description
Commit [1] (later refactored by [2]) hid the buttons which allow to edit the main website menu and custom website menus (as the ones in event pages), when using Odoo on a mobile device. Reading the…
Commit [1] (later refactored by [2]) hid the buttons which allow to edit the main website menu and custom website menus (as the ones in event pages), when using Odoo on a mobile device. Reading the code and related commits, this seemed to have been done for no apparent reason. After testing 16.0, it appears that menu edition from mobile devices was actually not working: the re-ordering UI was strangely hidden. After investigation, it appears that this was solved by chance, thanks to the unrelated commit [3] in 16.2. That commit indeed removes legacy CSS which was hiding all jQuery.ui.sortable UI elements by mistake. In 17.0, this was further improved anyway by not using jQuery.ui anymore (with [4]) and thus editing website menus from a mobile device works now perfectly... except that the buttons to open the menus edition dialogs were still hidden. This commit enables them. It was chosen to do it in 17.0 and not 16.2 as it is more an improvement than a fix in the end. [1]: https://github.com/odoo/odoo/commit/78c59afd133de8308f4eeb6e1a2a930d870878e7 [2]: https://github.com/odoo/odoo/commit/2dc82504e08cc370b67cdf1d580f26705870a085 [3]: https://github.com/odoo/odoo/commit/ee3e28987eb1ec23b8bacc7c4043d9690aada144 [4]: https://github.com/odoo/odoo/commit/a4b1c268131ed771dd68616a26a9f1ce50a189f0 Related to task-3645985
This update adds a database index to the account type field to speed up Profit & Loss report generation. The change improves report performance with minimal risk since the account type field is rarely modified and has few distinct values.
Original PR description
## Description Add missing index to speed up queries related to the P&L reports. As the report queries per `account_type` it's beneficial to have it indexed. The field is not write heavy, and has low count of distinct values ( since it's a selection field), so there is little downside of having it. It is meant to support the changes done in the related enterprise PR. ## Reference opw-3659497 Enterprise PR: https://github.com/odoo/enterprise/pull/53817 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#148490