Friday, March 6, 2026
36 changes · saas-19.2
New functionality added to Odoo
This update incorporates recent changes to Mexican city listings within the Odoo Enterprise system. This ensures accurate reporting and compliance for Mexican businesses utilizing the l10n_mx_edi_extended module. It maintains the system's data integrity regarding Mexican locations.
Original PR description
The Mexican government has recently introduced new cities. This pr adds those cities here as well. task-5883334 Forward-Port-Of: odoo/enterprise#109358 Forward-Port-Of: odoo/enterprise#107623
Enhancements to existing features
This update improves the user interface and simplifies maintenance for the Vietnam tax settings within Odoo. It updates tax information files, ensuring accurate calculations and a better experience for users in Vietnam. This change is part of a larger effort to enhance the Odoo platform.
Original PR description
For better UI and maintenance. task-[5904297](https://www.odoo.com/odoo/all-tasks/5904297) enterprise-[109478](https://github.com/odoo/enterprise/pull/109478)
Resolved issues and error corrections
This update addresses a technical issue within the Odoo `l10n_vn` module related to tax report testing. The change involves updating a tax label to ensure existing tests pass, improving the reliability of the tax reporting functionality for Vietnamese users. This resolves a previously failing test and ensures accurate reporting.
Original PR description
Updates in the `l10n_vn` module revised a tax label. We update it here to pass otherwise failing tests. task-[5904297](https://www.odoo.com/odoo/all-tasks/5904297) odoo-[251906](https://github.com/odoo/odoo/pull/251906)
This update adjusts the Romanian tax reporting within the Enterprise module to align with recent changes in the Core Enterprise (CE) version. The update removes outdated tax codes and adds new ones, ensuring accurate reporting for Romanian businesses. This ensures compliance with current tax regulations.
Original PR description
Some taxes were no longer needed in CE, so they needed to be removed task-5411745 Forward-Port-Of: odoo/enterprise#109606 Forward-Port-Of: odoo/enterprise#106127
This update enhances the Point of Sale system's ability to communicate with devices running on your local network (localhost). Specifically, it enables communication through LNA, allowing for easier testing and integration with local hardware. This improves development efficiency and simplifies troubleshooting.
Original PR description
This commit allows communication with devices running on localhost (127.0.0.1) through LNA task.5936854 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#251261 Forward-Port-Of: odoo/odoo#250972
This update enhances the accuracy of interest rate calculations for loans within the Enterprise module. Previously, interest rates were limited to two decimal places. Now, users can specify interest rates with up to ten decimal places, providing greater flexibility and precision for financial reporting.
Original PR description
Allowing more precision on the interest rate for loans. By default the display uses 2 decimals, but if a user decides to add more precision they can up to 10 decimals. task-5913175 Forward-Port-Of: odoo/enterprise#107163
This update streamlines the process of setting up tests within Odoo, making them more efficient and reliable. The changes focus on automating repetitive setup steps at the class level, which will help ensure the ongoing stability and accuracy of our core modules like L10n BE, HR Payroll, and Timesheet Grid.
Original PR description
Forward-Port-Of: odoo/enterprise#109679 Forward-Port-Of: odoo/enterprise#108739
This update resolves a recurring issue in the l10n_ph_reports_asset module's test suite. The problem stemmed from how daily depreciation calculations were handled, specifically when dealing with leap years, which caused intermittent test failures. This fix ensures accurate depreciation reporting, particularly during leap years.
Original PR description
The test suite fails intermittently due to leap years affecting daily -computed depreciation runbot-[241145](https://runbot.odoo.com/odoo/runbot.build.error/241145)
This update fixes an issue where highlight colors were difficult to see in Odoo's dark mode settings. The change ensures text is black, significantly improving readability and the user experience when navigating the settings interface.
Original PR description
Before this commit, highlights were not readable when searching on the settings in dark mode. Now, we force the text color to black to improuve the contrast and redability. task-id 6003446 Forward-Port-Of: odoo/odoo#251979
This update resolves a technical issue that prevented users from correctly ordering stock when using the replenishment multiple feature. The fix corrects a calculation error within the stock management system, ensuring accurate order quantities are generated. This improves the reliability of stock replenishment processes.
Original PR description
Backport of: https://github.com/odoo/odoo/commit/fe806166968d55a70f5bf335dcb3633e18d8ecc7 Steps to reproduce: - Create a storable product “P1”: - UoM: Unit and Pack of 6 - Purchase tab: add any vendor - Go to Replenishment and create a new rule: - Product: P1 - Min: 10 - Max: 100 - Replenishment Multiple: Pack of 6 - Select the line and click “Replenish” → “Order to Max” Issue: A traceback is raised: “TypeError: unsupported operand types in: uom.uom(2,) - 4.0” In `_get_qty_to_order`, we compute the quantity to order and then adjust it according to the replenishment multiple, but we try to Subtract the rounded remainder from the uom (which is a recordset) instead of the quantity (which is a float). opw-5947919 Forward-Port-Of: odoo/odoo#251756 Forward-Port-Of: odoo/odoo#250608
This update fixes a UI issue related to work order completion dates and excludes subcontracted productions from the Kanban view. These changes enhance the clarity and usability of the work order management process, ensuring accurate tracking and reporting.
Original PR description
A few UI Fixes. Fix date_finished when setting a workorder 'in progress'. Exclude subcontracted productions from Kanban view. task: 5945452
This update resolves an issue where work orders weren't correctly displayed in the Kanban view, particularly for subcontracted productions. It also fixes a bug related to accurately reflecting the status of work orders as 'in progress'. This ensures a more accurate and reliable view of work order activity.
Original PR description
A few UI Fixes. Fix date_finished when setting a workorder 'in progress'. Exclude subcontracted productions from Kanban view. task: 5945452
This update fixes several issues within the Odoo spreadsheet component, ensuring it's running the latest version compatible with the 19.2 release. These fixes improve the dynamic pivot table functionality and address minor UI inconsistencies, enhancing the user experience.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/ccf90d6262 [REL] 19.2.2 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/ccf90d6262 [REL] 19.2.2 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/5883e326cd [FIX] Dynamic pivot: header alignment [Task: 5922279](https://www.odoo.com/odoo/2328/tasks/5922279) https://github.com/odoo/o-spreadsheet/commit/a714ce64b1 [FIX] chart-panel: reset when changing panel [Task: 5926661](https://www.odoo.com/odoo/2328/tasks/5926661) Co-authored-by: Florian Damhaut (flda) <flda@odoo.com> Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Ronak Mukeshbhai Bharadiya (rmbh) <rmbh@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com> Co-authored-by: Marceline Thomas (matho) <matho@odoo.com>
This update adjusts the minimum and maximum amounts for employee mobility budgets each year, aligning with local regulations. The changes ensure accurate budget calculations and support employee relocation needs. This is a routine maintenance update.
Original PR description
Each year the minimum and maximum amount of mobility budget is indexed, here are the new values. Forward-Port-Of: odoo/enterprise#109641
This update fixes an issue where large category images in the Point of Sale selector would overflow, obscuring the category name. The change adjusts the layout to ensure images are appropriately sized, preventing overflow and improving the visual clarity of the selector. This enhances the user experience for product selection.
Original PR description
Before this commit, when a category image was too large, it would overflow and take all the space dedicated to the category name. Now we set the width of the image to 1/3 of the button and the name to 2/3, so that the image never takes too much space. task-id: 5462315 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#249368 Forward-Port-Of: odoo/odoo#242054
This update resolves a problem where Odoo couldn't send email templates without a linked record. A recent change in the core system caused this to fail. This fix ensures email templates can now be sent regardless of whether a record is associated, maintaining reliable email functionality.
Original PR description
Add explicit support for sending an email template with no actual record, i.e., calling `template.send_mail(False)`. This used to work but now fails since https://github.com/odoo/odoo/pull/227477. task-6000637 Forward-Port-Of: odoo/odoo#252076
This update fixes an issue where editing recurring events synced from Outlook would trigger unwanted emails to attendees. The change prevents Odoo users from directly modifying Outlook-created recurring events, streamlining the synchronization process and reducing unnecessary notifications. This improves the user experience and avoids potential communication overload.
Original PR description
## Issue: Recurring events created from Outlook should not be able to be edited from Odoo, this is because the changes made are going to be sending unwanted emails to the attendees. ## Steps to…
## Issue: Recurring events created from Outlook should not be able to be edited from Odoo, this is because the changes made are going to be sending unwanted emails to the attendees. ## Steps to reproduce: 1. Connect to Outlook and Sync for user A. 2. Create a recurring event from Outlook. 3. Connect into a user B with access to the event and edit all the events from the series. 4. Run the scheduled action to sync user A. 5. Many emails are going to be sent to the attendees from Outlook. ## Solution: With the current implementation, we are going to avoid editing for the users connected to Outlook, however any user with the access to that event in Odoo and that it has not synced with Outlook is going to be able to edit the event. To avoid this, we should check if the event is recurring and it has been created from Outlook, for this we are going to be looking for the event `microsoft_recurrence_master_id` which will be available only for the recurring events created from Outlook. opw-4374503 Forward-Port-Of: odoo/odoo#252079 Forward-Port-Of: odoo/odoo#199663
This update corrects an issue in the holiday test data, ensuring it aligns with country-specific work entry types. The changes involve moving incorrectly defined work entry types to the correct module, `hr_work_entry`, improving the reliability of testing and the overall functionality of the holiday scheduling feature.
Original PR description
In this commit, we address the issue of types being generic in the tests, when they should be country specific. Task-6004338 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 resolves an issue where deleting a workspace (folder) linked to a folder setting would trigger a database error. The fix prevents the deletion of these folders during the system's automatic cleanup process, ensuring data integrity and stability. This improves the reliability of the Documents module.
Original PR description
When a workspace(folder) linked to a folder setting is moved to the trash and the ``Base: Auto-vacuum internal data`` cron runs, a traceback will generate. Steps to reproduce the error: - Install…
When a workspace(folder) linked to a folder setting is moved to the trash and the ``Base: Auto-vacuum internal data`` cron runs, a traceback will generate. Steps to reproduce the error: - Install ``documents_account`` module - Go to Documents > Configuration > Files Centralization > Enable Accounting > Select any workspace > Save > - Click on Journals > Create a new > Select any Journal > Create a Workspace A > Save - Go to Documents > Click on Workspace A > Actions > Move to trash - Run the ``Base: Auto-vacuum internal data`` cron Traceback: ```py ForeignKeyViolation: update or delete on table "documents_document" violates foreign key constraint "documents_account_folder_setting_folder_id_fkey" on table "documents_account_folder_setting" ``` solution: override the ``_get_gc_clear_bin_domain`` method to exclude folders linked to folder settings, preventing their deletion during the garbage collection. sentry-7193540869 Forward-Port-Of: odoo/enterprise#109636 Forward-Port-Of: odoo/enterprise#104875
This update resolves an issue where users were seeing duplicate settings options (like 'Minimum Digits') when configuring widget types in Odoo Studio. The fix involves a technical workaround to prevent the duplication of label content generated by the underlying OWL2 framework, ensuring a cleaner and more consistent user experience.
Original PR description
steps: - Install Project and Studio - Open studio, add a decimal field - Click on it - There are two "Minimum Digits" instead of "Digits" & "Minimum Digits" Add dummy `t-set` nodes before `t-esc` directives in property sub-templates to prevent label content from being rendered twice. This is a known OWL bug (https://github.com/odoo/owl/issues/1610) where `t-esc` inside a named slot gets duplicated. Since the issue lies in the OWL2 framework itself, a `<t t-set="__dummy"/>` is used as a workaround to break the duplication pattern in owl2. opw-5974611 Forward-Port-Of: odoo/enterprise#109694
This update resolves an issue where commission reports were incorrectly handling large numeric IDs, leading to potential data conflicts. By ensuring the full ID is always used, the system now accurately identifies and manages commission records, improving report reliability. This fix addresses a technical problem that could impact commission calculations.
Original PR description
In commission report, we need unique ids for achievements and commissions. We avoid using row_number because it becomes really slow when the amount of records increases. That's why we need reliable unique ids, build from the account move line/sale order line/sale order log, user_id, commission rules. As it represents a lot of information stored inside a unique integer, bigint are necessary. It works great in python because int() can be used to handle bigint but JavaScript is not great with that. It will cast the value sent by the ORM silently and as a result, when the ORM is called back by the JS framework, it will pass a truncated id that either conflict with another record or may not exists (ids are generated using recipe). This commit ensure that the full id is always accessible and is used to browse records when the framework js contact methods. task-5973128 Forward-Port-Of: odoo/enterprise#108751
A bug preventing users from correctly setting the fiscal year month and day for companies with child companies has been resolved. The fix ensures that all related data is updated before validation checks are performed, preventing a misleading error message.
Original PR description
Having a parent company and a chid company selected, and changing both the last day and the last month of the fiscal year as the same time raises a ValidationError. This is because in this case, in the write we successively modify each changed delegated fields from root company to the branches. Then, when checking the constrains we loop through all delegated fields and check if the value of the branches are the same as the root company. This check triggers the error as all values are not set yet. By using a write on branches for all changed delegated fields instead of a simple assignation, the constrains check occurs once all the value have been updated. Steps: - Have a root company and a branch - Select both in company selector - Go to Accounting configuration - Change fiscalyear last month AND ast day at the same time - Save -> ValidationError in `_check_root_delegated_fields` opw-5431145 Forward-Port-Of: odoo/odoo#252171 Forward-Port-Of: odoo/odoo#241413
This update prevents Instagram posts from failing due to delays in media processing. We now use a scheduled cron job to automatically retry publishing when a container isn't immediately ready, ensuring posts are successfully created. This improves the overall reliability of Instagram posting functionality.
Original PR description
With the current behavior the Instagram API sometimes requires time to process media containers, the media_id is not yet ready on Instagram side, leading to failed posts. To avoid this, we now use an asynchronous flow: If the media container is not immediately 'FINISHED', we store the container ID in `instagram_post_id` (prefixed with `containerIDs-`), set the state to 'posting', and trigger the scheduled cron to retry in 1 minute. The `_cron_publish_scheduled` method has been updated to detect these pending posts and resume the publication attempt so workers remain free while Instagram processes the media. opw-5081325 Co-authored-by: @ushyme Forward-Port-Of: odoo/enterprise#100313
This update corrects a bug in the HTML editor's test suite that caused inconsistent test results due to overly long timeouts. By using a more robust waiting mechanism, the test now reliably identifies regressions when the toolbar isn't displayed correctly, ensuring greater stability.
Original PR description
Because a timeout in js only ensures to wait at least for that amount of time while giving no upper bound to the actual awaited time, it was possible for advanceTime(100) to actually wait for more…
Because a timeout in js only ensures to wait at least for that amount of time while giving no upper bound to the actual awaited time, it was possible for advanceTime(100) to actually wait for more than 300ms when the runbot was slow enough. In that case, since enough time has elapsed between the action and checking that the toolbar hadn't opened yet, well it was actually already opened, since we had waited too much, and the test failed non-deterministically. This is actually a special case here. Usually we want to use `waitFor` or `expectElementCount` with the toolbar since it's a popover and is therefore affected by [1]. But we cannot use them to check if the toolbar hasn't opened too early, lest we find ourselves with the same problem than explained above. Using only advanceTime with a timeout of 100ms and a synchronous `expect` check ensures that, in the general case when the runbot is fast, the test will fail in case of a regression, since there would have been ample time to have multiple animation frames during 100ms. The regression will only be hidden when the runbot is very slow and no animation frame has happened during the 100ms timeout, which is an acceptable tradeoff. The same issue appeared in another test so I fixed it as well. Timeouts throughout this test file were excessive, with multiple uses of `advanceTime(500)` while OPEN_TOOLBAR_DELAY is 300ms. This is because the commit dates from before [1] and so it was hard to ensure that enough time and animation frames had passed before we could check with `expect`, which is synchronous. Now we are using `expectElementCount`, which uses `waitFor` under the hood which has a proper mechanism to wait for enough animation frames with an additional internal delay. With these, there is no more need for a manual timeout to exceed the value of OPEN_TOOLBAR_DELAY. Note that this only applies to the cases where we check that the toolbar should be displayed, since cases where it should NOT be displayed before a certain timeout should NOT use those utils, as explained above. runbot-238562 [1]: https://github.com/odoo/odoo/commit/54da715df84789f9a1acc0cfc91be41dcdbab140 Co-authored-by: Sébastien Geelen <sge@odoo.com> Forward-Port-Of: odoo/odoo#247551
This update corrects a visual issue where the unit display (hours/days) for KPIs in the timesheet reporting was misaligned. The change restores the original layout, ensuring accurate and consistent KPI reporting for users. This resolves a minor display problem impacting the clarity of timesheet data.
Original PR description
Due to the recent refactoring of the `formatFloatTime` formatter in odoo/enterprise#108072, the KPIs lost their layout, resulting in a misaligned display. This commit restores the original layour for the KPI header, ensuring the unit (hours/days) is correctly shown next to the value.
This update resolves an issue where avatars in collaborative lists (like 'To Do' notes) were consistently displayed on the first line, regardless of where the user was viewing the list. The fix ensures avatars now correctly follow the user's focus within the list, improving the user experience. This change was implemented to maintain consistent visual alignment and usability.
Original PR description
Since [1] when using collaboration, the position of the avatar for list items is always displayed on the first line - instead of following the user's focus. This commit fixes this by only applying the patch of [1] when inside an embedded component. Steps to reproduce: - Go to a "To do" note - Add a checked list with indented items - Access the same note from another window - Move around the checked list and observe avatar in other window => Avatar remained on first line while moving around list items [1]: https://github.com/odoo/odoo/commit/9863cb25d6dfdba224897f21634bdaaf3eca91a7 task-5930388 Forward-Port-Of: odoo/odoo#248438
This update fixes an issue where tax reports generated in Belgium were producing negative values in XML files for carried over tax lines. The change ensures that only positive amounts are included in the XML, resolving a potential reporting discrepancy. This improves the accuracy of tax reports.
Original PR description
When generating the xml for tax report, negative values should not be present in the xml for carried over lines (81, 82, 83, 86, 87, and 88) Steps: - Create a RBILL for today - 1 month, add an invoice line with tax using one of the following tags: -81, -82, -83, -86, -87 or -88 in its base refund repartition line - Open the tax report on the month of the RBILL - Generate the xml, either by the dedicated button, or by creating and posting the closing entry -> there is line(s) for negative amounts opw-5955323 opw-5428395 Forward-Port-Of: odoo/enterprise#109568 Forward-Port-Of: odoo/enterprise#108916
This pull request optimizes test execution by streamlining setup processes and reducing unnecessary logging. Specifically, it consolidates setup steps, eliminates redundant HTTP thread usage, and suppresses excessive password reset logging, resulting in faster and more efficient test runs.
Original PR description
- move a bunch of expensive setUp to setUpClass - backport #152378 to avoid password keying in 17.0 also Forward-Port-Of: odoo/odoo#252248 Forward-Port-Of: odoo/odoo#250667
This update fixes a bug preventing warnings on the EC Sales List report when dealing with customers outside of Europe. Specifically, the report now correctly identifies customers with 'Intra-Community' fiscal positions in European companies and those using non-European delivery addresses, ensuring accurate reporting and compliance. This ensures accurate sales reporting for international transactions.
Original PR description
The warnings partner_same_country and partner_no_ec_country on the EC Sales List are never showed. To Reproduce (for partner_same_country warning): - Create a company in Belgium - Create a customer in Belgium with "Intra-Community" as a Fiscal Position - Create an invoice with this customer - Go to the EC Sales List - The customer doesn't appear in it, so the warning is not present. For the partner_no_ec_country, do the same but with the country of the customer being one outside of Europe. Forward-Port-Of: odoo/enterprise#107139
This pull request corrects a minor issue in the German localization (l10n_de) module where tags were incorrectly formatted in the account data file. This ensures accurate reporting and categorization of financial transactions for German-speaking customers. The fix was verified and approved as part of a standard process.
Original PR description
Commit db0d499952192ede0def2a070e103ba67952387c inverted some tags which is wrong opw-5415426 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#250744
This update fixes an issue where tax report tags were incorrectly sorted, preventing proper auto-completion functionality. The team has also improved testing to prevent similar errors in the future. This ensures accurate reporting for German tax compliance.
Original PR description
Commit https://github.com/odoo/odoo/commit/db0d499952192ede0def2a070e103ba67952387c inverted some tags which is wrong Tags must be sorted for the auto complete to work properly Improving tests to catch more errors opw-5415426 Forward-Port-Of: odoo/enterprise#108848
This update removes a display field ('Visible Internally Only') from the customer rating form in the Helpdesk module. This field was no longer needed since customer ratings are no longer visible on the website. This change improves the user experience and reduces unnecessary data display.
Original PR description
**Steps to reproduce:** - Open a Helpdesk ticket with a customer rating. - View the rating form. - Observe the field ‘Visible Internally Only’ still showing. **Issue:** - The field is displayed even though ratings are no longer shown on the website. **Reason:** - The field is now irrelevant but still present in the view. **Fix:** - Invisible the ‘Visible Internally Only’ field from the customer rating form in the affected version. **Task id - 5359052** Forward-Port-Of: odoo/enterprise#109287 Forward-Port-Of: odoo/enterprise#100686
A bug causing duplicate 'New' and 'Create New' buttons in the task list has been resolved. This change ensures users only see a single 'New' button when creating tasks, streamlining the process and preventing confusion. The fix addresses a technical issue related to a ControlPanel refactoring.
Original PR description
Steps to Reproduce --- 1. Enable Task Dependencies in Project settings 2. Create project with no task templates 3. Open task form -> Blocked By tab -> Add a line 4. Observe duplicate "New" and "Create New" buttons Issue --- - The task list view displays both “New” and “Create New” buttons, resulting in duplicated creation actions. Current Behaviour --- - Two different creation buttons are displayed simultaneously Expected Behaviour --- - Only a single “New” button should be displayed Root cause --- - ControlPanel refactoring removed props.showButtons without adding !env.inDialog check to task views. Fix --- - Add !env.inDialog check , this prevents the ProjectTaskTemplateDropdown component from rendering in dialog contexts, eliminating the duplicate button issue. Related - https://github.com/odoo/odoo/pull/220325 task - 5403917 Forward-Port-Of: odoo/odoo#241628
This update adds a temporary field to the burndown chart in the project module. This resolves a technical issue that would have prevented a safe upgrade to the latest version of Odoo. It ensures future updates to the burndown chart functionality can be implemented without disrupting existing data.
Original PR description
Add an empty `python_method` field to the burndown chart embedded actions as a preparatory change for a safe upgrade path. Without this, replacing `action_id` with `python_method` in master would temporarily violate the SQL constraint on `ir.embedded.actions` that prevents both from being set simultaneously. references: #239000 task-5347524 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#252145
This update resolves an issue where customers using customized account settings would receive empty depreciation schedule reports. The fix ensures accurate report generation by granting administrative access to verify compatibility with Odoo's accounting rules, preventing incorrect report output.
Original PR description
Following odoo/enterprise@ece0405785, in case a customer modified the `account.move.line` record rules in a way which is incompatible with the AML shadowing, user will only get an empty deprecation schedule report. This commit as a sudo, to ensure we get a correct report, access rights being already check for `account.asset` records. Forward-Port-Of: odoo/enterprise#108901
This update fixes an issue where link popovers in the preview mode were excessively large, particularly when titles were long. Now, the popover size is consistently maintained, providing a cleaner and more user-friendly preview experience. This ensures consistent visual presentation across different content lengths.
Original PR description
Before this commit: the link popover is oversize when the preview has long title. After this commit: the link popover retains its size. task-6000052 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#252045