Friday, March 1, 2024
4 changes · 17.0
Enhancements to existing features
This update improves the performance of deleting planning shifts in the system. When deleting shifts, especially recurring ones, the system was performing slow database scans. We've added database indexes to speed up these deletions, which is particularly beneficial for companies with large timesheet and work entry records.
Original PR description
## Description Deleting planning slots can be slow on some databases that make heavy usage of the Timesheet/WorkEntries from shifts feature and/or they have large tables for their `account.analytic.line` and/or `hr.work. entry`. It can be especially felt when deleting all recurrences of a shifts. This is due to the missing indexes on the FKey to the `planning.slot` model on large models. Without an index on the FKey, deleting a `planning.slot` will trigger Seq.Scans on the tables that references the `planning.slot` model to set the field to NULL or trigger the SQL `ON DELETE` constrains. ## Fix Add the missing indexes. Partial on nulls because it's a sparse relationship. ## Reference task-3747131
This update removes restrictions that previously prevented users from modifying taxes that were already used in transactions. Instead of having to duplicate a tax to make changes, users can now edit taxes directly. The system maintains a detailed audit trail of all modifications, and the change tracking has been improved to focus on the position of tax components rather than their IDs, reducing unnecessary notifications.
Original PR description
Problem --------- Due to commit 8d77045b46a1b4a9d7fffd1111e53749d51d81e2, restrictions were added to taxes that were used in transactions. However, this behavior worsens user experience; users that…
Problem --------- Due to commit 8d77045b46a1b4a9d7fffd1111e53749d51d81e2, restrictions were added to taxes that were used in transactions. However, this behavior worsens user experience; users that would like to modify a tax would have to duplicate it, update the duplicated version and modify the tax usage where necessary. For such reason, this process is being reverted (we keep the tracking of the modification). The tracking of repartition lines now also includes the sequence of the lines since it is not restricted anymore. Furthermore, `_message_log_repartition_lines` has been updated to log messages when new repartition lines are added or repartition lines are removed. It also has been update to track changes of lines by comparing their position in the tax (rel. sequence) and not their IDs. Doing so allows to remove unnecessary logging when, for example, users remove a repartition line and immediately add a new one similar to the one deleted. It also allows to not log reordering event of two similar lines. original-commit: 8d77045b46a1b4a9d7fffd1111e53749d51d81e2 task-3450002 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves the website creation experience by adding a helpful placeholder text to the industry selection field. Users will now see a hint about what to enter when creating a new website, reducing confusion and making the setup process more intuitive.
Original PR description
-User might not know what they going to type in, this commit add a placeholder in the input of industry selection to give a hint for user when in website creation 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 removes event booths from the website sitemap to improve search engine efficiency. Search engines will still discover booth pages naturally through website crawling, so explicitly listing each booth in the sitemap is unnecessary. This reduces unnecessary crawler requests and improves overall site performance.
Original PR description
If booth exists for this event, bot will discover it via crawling. Don't need to ask to crawler to check for each event if a booth exists. 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