Daily updates from Odoo
Tuesday, October 1, 2024
45 changes · 18.0
Resolved issues and error corrections
This fixes a visual flicker on status icons when users hover over items in the compact Discuss sidebar. The change makes the interface feel steadier and more polished without changing any workflow or functionality.
Original PR description
Mouse-hovering items when discuss sidebar is compact result in some style flickering on im status icon. This happens because the items are button and they need `bg-inherit`. Due to CSS specificity, however, the classname is not enough, so we need `!important` in CSS, which is what this commit does to fix the issue. Before / After (see status of 3 items at the bottom while mouse-hovering)  
Website editors can now drag blocks near the bottom of a long page and have the page scroll as expected. This restores smoother page editing when building longer website pages.
Original PR description
Steps to reproduce the bug: - In website edit mode. - Add enough blocks to the page so that a vertical scrollbar appears. - Drag a block and move it to the bottom of the page to scroll down. - Bug:…
Steps to reproduce the bug: - In website edit mode. - Add enough blocks to the page so that a vertical scrollbar appears. - Drag a block and move it to the bottom of the page to scroll down. - Bug: The page does not scroll. This bug was introduced because the scroll element is now the `<html>` instead of the "#wrapwrap" element (Since this commit [1]). The issue arises because "getBoundingClientRect()" gives the distance from the top of the element to the viewport, excluding the scroll position, while the `<html>` element accounts for scrollTop to define its Y position. In this commit, we also fixed the "dragStart" function, which didn't return the HTML element as the scroll element when it was the drag and drop container. The issue is that the "closestScrollableY" function don't consider an element with "overflow: visible" as scrollable. At first, we tried to modify "closestScrollableY" to consider an element with "overflow: visible" as scrollable, but this caused several errors in the "drag and drop" QUnit tests and we couldn't find the cause. This needs further investigation. To fix the issue, we updated the "dragStart" function to check if the "drag and drop" container is the "ownerDocument.scrollingElement". If it is, we use that element as the scrollable element for the "drag and drop". [1]: https://github.com/odoo/odoo/commit/189a7c96e6e26825dc05c0c6466576fe63aa091e task-4190506
Opening the Dashboard app no longer triggers an access error for newly created non-admin users. This ensures users without administrator rights can access dashboards as expected in a fresh database.
Original PR description
Steps to reproduce - install a fresh database, without any demo data - create a new user which shouldn't have admin rights - connect as this new user - open the Dashboard app => Access Error The `ir.model` cannot be read by anyone, except admin users. Task: 4224689 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resetting a payment to draft now also resets its linked journal entry, and deleting a payment removes the linked journal entry too. This prevents orphaned accounting entries and keeps payment records synchronized with the accounting ledger.
Original PR description
Reset to Draft and Payment deletion should impact the linked Journal Entry as well, or we'll just leave a bunch of created entries that will be lost in Accounting. Reset it to draft => Reset to Draft the Journal entry as well, no error message. Delete the payment => Delete the Journal entry We also revert the suppression of the synchronisation of the payment to move. And in the _get_trigger_fields_to_synchronize we remove is_internal_transfer since the field is no longer there. (https://github.com/odoo/odoo/commit/01b87f1230beac0568f4e3b1b76e547909506892) task: https://github.com/odoo-dev/odoo/commit/4215217583c566cc5188d71dcbbd7b1cd860b3ae --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website page properties menu no longer shows a publishing option that could make pages appear unpublished while still leaving them in the sitemap. This avoids misleading website managers until a more reliable solution is available.
Original PR description
Commit [1] introduced the possibility to publish/unpublish "any route" by using the visibility and groups fields available on the rendered view. This obviously had its limitations, indeed the route…
Commit [1] introduced the possibility to publish/unpublish "any route" by using the visibility and groups fields available on the rendered view. This obviously had its limitations, indeed the route and the view are independent (e.g. a same URL could lead to different views depending on values in the database for example) but allowing to "unpublish" the "current rendered page the user is seeing" seemed like a good first improvement anyway. However, the sitemap was forgotten... and it is proving difficult to fix in a way that makes sense. It would mean saving the info of the URL that was used to reach the "unpublished" *view* in the first place somehow somewhere... and if it were to be possible, controllers with parameters, or controllers that lead to different views depending on some configuration would really be a problem. We choose to disable the feature for now (keeping its code but just not showing the possibility via the UI). We will revisit this later. In the end [2] added the possibility to properly "unpublish the whole shop" (not just one page), which is the main demand when it comes to unpublishing controllers (funny enough, the sitemap was also forgotten for that feature, before fixes [3] and [4]). [1]: https://github.com/odoo/odoo/commit/e3b1ff6e25ecc71c9242d3826cee09c636bc465a [2]: https://github.com/odoo/odoo/commit/5bde2e42c8ec5e943a779ad4b3e1b7142f2d2fcf [3]: https://github.com/odoo/odoo/commit/0738e0210207397429826ab3c4b3760b3a4dff44 [4]: https://github.com/odoo/odoo/commit/eb14c1f401d5d09a1d906346a4a4cd494bb47628
Fixes issues in the website page properties dialog so users can clone or delete pages successfully. It also makes redirect options appear immediately when editing a page URL, reducing confusion during website page setup.
Original PR description
Moved out of https://github.com/odoo/odoo/pull/181224
The Discuss sidebar call icon now has better spacing when displayed with a border. This small visual fix makes the interface look cleaner and easier to scan for users.
Original PR description
Before / After <img width="296" alt="Screenshot 2024-10-01 at 16 26 22" src="https://github.com/user-attachments/assets/b7b23378-b778-4610-ba8d-83f3219e7234"> <img width="299" alt="Screenshot 2024-10-01 at 16 25 57" src="https://github.com/user-attachments/assets/08cf20af-fb75-4ddf-ae25-3d5f5d1c241a">
This fixes an issue in Point of Sale where floating orders were not listed alphabetically by their assigned names. The system now uses the current order name field, making it easier for staff to find and manage multiple open orders.
Original PR description
Steps to reproduce : -------------------------- - Install the point_of_sale module. - Place orders on two or more floating orders. - Give the orders some name. Issue : --------- The floating orders are not sorted according to alphabet properly. Cause : ---------- The field containg floating order name is changed but, at this place still try to sequence by old name. [Referance PR](https://github.com/odoo/odoo/pull/175535) Fix : ----- Now updated the field name properly from note to floating_order_name.
The HTML editor no longer shows advanced text style options that are not currently supported in the website builder. This reduces confusion by hiding controls that are not relevant until the website builder moves to the new editor.
Original PR description
Currently, showExtendedTextStylesOptions are still displayed. Before the new editor (html_editor), it was only used by the website builder. The website builder still doesn't use html_editor, so we're going to disable them. We'll reintroduce them when the website builder uses html_editor. 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
Manufacturing orders now correctly treat BOM lines linked to an operation as manually consumed components. This prevents materials from being consumed automatically when an operation-specific component should be handled manually, improving production accuracy.
Original PR description
When an operation is added to a BOM line, it will be treated as a manual consumption component. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Purchase quotation accept and decline actions now consistently use the same secure portal flow, whether users click from an email or the portal sidebar. This prevents sidebar actions from failing and makes the confirmation feedback clearer for users.
Original PR description
There is two ways of confirming/declining a reception mail through the portal. Either by clicking on the sidebar or clicking on the button in the mail. While it works correctly when going through the mail link, as it goes through the controller that checks the access rights before preparing the order if the access token is good. However this didn't happen when using the buttons from the portal sidebar, as we don't go through the controller in this case. Unified both ways to always go to the controller. Also changed the feedback for accepted/declined quotations, so that's more visible for the user. Task-4207380 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editor building blocks now have more accurate keywords, making it easier for users to find the right content elements. Keywords that are no longer useful after the sidebar search removal were also cleaned up, reducing maintenance noise without changing business workflows.
Original PR description
This PR updatsd snippets keywords ensuring they accurately reflect the associated content. It also removes inline-snippets' keywords' because, following the removal of the sidebar's search, these are no longer necessary. task-4063510 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Starting an onboarding tour from a direct URL now correctly loads its step-by-step guidance. This prevents users from seeing an incomplete tour and helps onboarding flows work as expected.
Original PR description
When starting tour by url, if the tour was an onboarding tour (info in db and steps in registry), the steps were missing. Now, if the steps are missing, I search them in the registry. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update streamlines several automated walkthrough tests by removing repeated or unnecessary actions and reducing waiting time between checks. It helps the test suite run faster and more reliably without changing business features or user workflows.
Original PR description
In this commit, we : - Remove redondant steps (multiple click on the same element) - Remove unuseful clicks (default action is now "nothing") - Impose checkDelay so that tours go faster (checkDelay is 750ms by default)
Sale orders created from completed repair orders now carry over the actual quantity completed in the repair. This ensures customers and staff see accurate delivered quantities when confirming those sale orders.
Original PR description
Steps to reproduce: - Create a repair order. - Add a stock move to it with any quantity. - Confirm, start and end the repair order. Make sure that quantity done is positive. - Generate a sale order from the repair order. - Confirm the sale order. Expected result: `qty_delivered` of the generated sale order line should be the same as the quantity done of the move in the repair order. Current result: `qty_delivered` is zero. 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 fix ensures tax totals stay accurate when a currency's rounding settings have been changed. It also corrects price-included reverse charge tax calculations, reducing small invoice discrepancies that could affect accounting totals.
Original PR description
The test was computing: 20000 * 2.82 / 1.1726 = 48098.24 48098.24 * 0.21 ~= 10100.63 When splitting to tax repartition lines, we get 10100.65 because of the rounding set on the currency. The error is computed as 10100.63 - 10100.65 = -0.02 so 2 x -0.01 to distribute. Before this commit, we had the time to fix only one rounding error so: 10100.65 - 0.01 = 10100.64 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The dashboard edit option is now only provided by the edition module that supports it. This prevents users from seeing an error when opening a dashboard in installations that do not include the editing add-on.
Original PR description
Steps to reproduce: - Install spreadsheet_dashboard without spreadsheet_dashboard_edition - Go to a dashboard - Click on the edit button => Traceback This commit moves the edit button to the right module (spreadsheet_dashboard_edition). Note that to avoid overriding DashboardAction (component, template and entry in the registry), we introduce a new registry with the aim to contains the edit button. 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 fixes how tax totals appear on invoice PDFs and corrects related tax total handling for Hungary. It also makes global rounding the default for Mexican localization, helping invoices follow local expectations more consistently.
Original PR description
[FIX] account: Fix wrong condition to display tax_totals on PDF [IMP] l10n_mx: round_globally in mexico by default Now the round globally is fully managed, let's enforce it in Mexico. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Project and timesheet task cards now display footer details more neatly. Assignee names are shortened when space is limited, the remaining-hours indicator blends better with the page, and outdated styling was removed for a more consistent look.
Original PR description
**Before this commit:** - The assignee's name would overflow instead of truncating in the footer. - The remaining hour's widget displayed an unusual grey background. - classes with the prefix `oe_` were present for styling. **After this commit:** - The assignee's name will now truncate after a specific width in the footer. - The remaining hour's widget has a transparent background. - removed class `oe_kanban_align` from the code base. Task-4207390
Website dynamic snippets now keep a balanced layout when they show only one item, such as a product or appointment. This prevents the item from stretching too wide or becoming overly tall, improving page appearance and readability.
Original PR description
Prior to this this commit, when a single element was fetched in the dynamic snippet, it took the entire width and became too tall according to the page height. (e.g. Products or Appointments snippet) To limit the height of this snippet, this commit forces the same size to be used as when two elements are fetched. task-4215773 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Using the Manufacture button from a Bill of Materials overview now creates a manufacturing order without incorrectly moving serial-numbered products into an in-progress state. This keeps the workflow consistent with creating a manufacturing order manually and then selecting the same Bill of Materials.
Original PR description
The Manufacture button added in the BoM Overview prepares a new manufacturing order using the bom. However for serial products this has a drawback of changing the state to 'in progress'. This is not the case when creating a new manufacturing order and then selecting the same bom. The origin is within '_onchange_producing / _set_qty_producing' and the way the record is initialized: - from 'Manufacturing orders / New' all fields have their default values - from 'BoM Overview / Manufacture' the bom_id and related fields are set. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The table editing menu now includes the missing Reset Size option again. This helps users quickly return tables to their default sizing after editing, improving consistency in content editing.
Original PR description
The Goal of this commit is to add the “Reset Size” table menu item that had been omitted during conversion to html_editor.
This change fixes how saved text is loaded into forum and profile text areas. It avoids an extra server lookup, helping these pages show existing content more reliably and efficiently.
Original PR description
This is a partial revert of [1] and proposition of another solution. Instead of doing an extra orm call we just add the content as attribute to the textarea and retrieve it directly from there. opw-4148163 [1]: https://github.com/odoo/odoo/commit/82fbc0c30848763d6a55d4e5e78b0b34ff6c8245
This fix makes the editor's command search close properly when users press Escape. It prevents the search panel from unexpectedly reopening when the user continues typing, making text editing smoother and less confusing.
Original PR description
Before this commit, pressing “escape” when the powerbox is open did not stop the current search. Adding a new character reopened it. 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 fixes the Time Off accrual plan view so the carry-over validity value is no longer shown when no validity period is configured. It reduces confusion for HR users by only displaying relevant leave policy information.
Original PR description
in this commit, fixes a issue where carry over validity isn't set value is still visible in view. task-4207945 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 corrects how expected working hours are recalculated when overtime records are updated. It helps keep attendance and overtime figures accurate for employees and payroll-related reviews.
Original PR description
Expected hours were not recomputed properly on the _update_overtime method
This fixes a display issue in Frontdesk kiosk mode where the landing page did not fill the full browser window. The change improves the visitor check-in experience by making the kiosk screen look complete and consistent.
Original PR description
This PR addresses a styling issue in the kiosk mode of Frontdesk. Before this pr, the landing page would not fill the height of the window causing the whole user experience to be strange. task-4213241
This fixes an issue where links to employee documents were missing or incorrect in HR document communications. Employees and HR teams can now access the intended documents more reliably from the related messages or pages.
Original PR description
We forgot to add the field. We'll go for a model method in this fix, this can be cleaned to a field in master. Task-4216195
Copying previous weeks in Planning now handles open shifts without errors, including shifts spanning multiple days. Shifts outside an employee's normal schedule are copied as open shifts unless the employee is fully flexible, making schedule duplication more predictable.
Original PR description
Before this commit, when the user copy shifts of the previous weeks and in that previous week he has an open shift, he will have a traceback will be raised because we check if the resource of the shift is flexible or not to be able to correctly compute the allocated hours of the splits generated with the split to split. The problem is an open shift has no resource so it is no needed to check if the resource is flexible. This commit checks if the shift is an open shift or not before checking if the resource is flexible or not. This commit also fixes another when we try to copy previous an open shift planned during 2 days, the allocate hours is computed based on the company schedule instead of the real time span between the date end and date start as we do in the `_compute_allocated_hours` method. task-4207839
This update corrects tax total display on Ecuador withholding PDFs and stabilizes Mexico electronic invoicing tests so they are no longer affected by date changes or recent merges. It also makes global rounding the default for Mexico, improving consistency with local invoicing requirements.
Original PR description
[FIX] l10n_ec_edi: Fix wrong condition to display tax totals in PDF [FIX] l10n_mx_edi: Fix broken test after merge: The fix has been added by https://github.com/odoo/enterprise/commit/d5da2b62263f85fbce0f2548085c066cbbf10371 At the same time, this commit has been merged: https://github.com/odoo/enterprise/commit/00cc171c6e122118af72d84bb26ff083c086dff4 Now those tests are skipped on runbot. Let's fix them. [FIX] l10n_mx_edi: Remove date related stuff from MX test files Now we move to october, the test is failing on runbot... [IMP] l10n_mx: round_globally in mexico by default Now the round globally is fully managed, let's enforce it in Mexico.
The dashboard edit button has been moved into the updated dashboard controls so it appears where users expect it. This keeps spreadsheet dashboard editing available after related interface changes, reducing confusion for users who manage dashboards.
Original PR description
This commit is the counterpart of https://github.com/odoo/odoo/pull/182079 and add the edit button to the newly introduced registry.
Sales order spreadsheets now leave out section headers and notes from line item lists, avoiding confusing or poorly formatted rows. The list is also inserted with table styling again, making spreadsheet views clearer and easier to read.
Original PR description
Sections and notes in the SO are badly displayed in the sale order line list in the spreadsheet. They should be excluded from the list (domain on display type). (or maybe later, change the default list fields to make it pretty somehow?) Task: 4200539
The report editor's table menu now disappears again when the pointer moves away, matching the previous expected behavior. It also closes during scrolling, reducing visual clutter and preventing the menu from staying open at the wrong time.
Original PR description
Since PR odoo/enterprise#181141, when a qweb table menu is displayed, it no longer disappears when the pointer moves outside it. This commit will reintroduce the old behavior: - When the pointer quits a closed qweb table menu, we make it disappear. - When the pointer leaves an open qweb table menu, it doesn't disappear. You need to do a pointerdown to make it disappear. We'll also add a close to the qweb table menu when scrolling. This will have the same behavior as the table menu.
Fixes issues in Odoo Studio where editing Kanban cards after adding a card menu could target the wrong part of the card. It also places ribbon elements correctly so card layouts remain visually intact, making customization safer and more predictable for users.
Original PR description
Before this commit there were two issues: - add a menu on a card - try to remove or add a field elsewhere in the card => the xpath of the last operation was always wrong. This was because the normlalise function got confused and refused to actually add the menu template before the card template. - web_ribbon was appended to the card => this cause the style to be broken. Albeit the ribbon widget makes sense at the top of the card template, it should not break the style in those proportions. So, a small fix is done in studio to add the ribbon at the top of the card, but we strongly recommend a fix that will enable to put it anywhere as a direct child of the relevant view node. task-4207793
This update cleans up and speeds up several automated test tours used to verify key workflows in Knowledge, Rental product configuration, and Web Studio. It helps reduce unnecessary test steps and makes validation faster and more reliable without changing customer-facing features.
The accounting reports quarter filter now calculates periods based on actual calendar quarters instead of counting three-month ranges from the current date. This helps users see accurate quarterly report data and reduces the risk of misleading financial analysis.
Original PR description
The quarter filter was not properly calculating the quarters. It was taking periods of 3 months not based on quarter but based on the current date. The months are now properly calculated based on the quarter.
This fix prevents the Documents accounting flow from creating unnecessary empty accounting entries when determining the right journal. It reduces clutter and helps keep accounting records cleaner without changing the intended user workflow.
Original PR description
We don't need to create an empty move to compute the suitable journal_id. Task-4216195
Portal users can now search or group helpdesk tickets by related sales orders without running into an access rights error. This removes an unnecessary restriction so customers have a smoother self-service support experience.
Original PR description
Prior to the fix, portal users would get an access rights error whenever they would group or search sale order. That was because the ``sale_order_id`` field was only given access to sale and accounting users. That was the case since the helpdesk app was first created. All users, including portal, have access to the ``sale_order_line`` field, thus the restriction on the ``sale_order_id`` field are not anymore necessary. We "fix" the access right error by basically removing the group restriction on the ``sale_order_id`` field in the helpdesk.ticket model. task-4207628
The Documents app no longer automatically applies the filter that hides shortcuts in search results. This reduces confusion by showing users a more complete and expected view of their documents unless they choose otherwise.
Original PR description
It's more confusing than helpful to enable the filter automatically. Task-4216195
This update fixes issues in sales commissions where switching a commission plan from achievement-based to target-based could behave incorrectly after returning it to draft. It also ensures subscription sales based on recurring revenue are reflected in the user’s commission view, improving confidence in commission tracking.
Original PR description
- When you select based on achievement save, then draft again and change it into based on achievement to based on targets - When I try commission plan based on MRR and try to sell sub, I don't see my commission in "my commission"
This update fixes issues in Documents where users could hit an access error when creating shortcuts to shared files located in folders they cannot edit. It also improves how the app opens to the correct folder or section at startup, making navigation more reliable.
Original PR description
In this PR, we fix the creation of shortcuts in My drive when the target are in non-writable folders. In a second commit, we fix and test the initial data folder_id passed to open the side panel on the right folder or section at the app's initialization. Task-4216195
The Documents app now refreshes its folder list after actions such as creating shortcuts, duplicating, archiving, or renaming folders. This prevents outdated folders from remaining visible and helps users see the correct document structure immediately.
Original PR description
Before this commit when creating shortcut / duplicating / archiving / renaming a folder the search panel wasn't reloaded and thus the folder still appeared in it. This commit fixes this. Task-4219258
Duplicating a financial report now creates a clearer copy with “(copy)” added to the name and includes the related budget lines. This helps users create new financial budgets from existing reports without manually rebuilding the structure.
Original PR description
Enable the copy of a financial report. Right now, when duplicating a financial report (or several at the same time), only the name is copied (same name, not even a "(copy)" after. We want to improve it by adding this "(copy)" in the title, and also copy the budget lines. This will enable a user to not start from scratch every time he wants to create a new financial budget. task-4207202
The Documents control panel buttons now display with consistent grouping and styling. This prevents visual glitches when only certain action buttons, such as Share, are shown.
Original PR description
Some btn-group classes were missing creating inconsistent looks among the buttons. The presence of the xpath for the share and freeze btn breaks the style when there are only the actions and share btns to display on the ctrl panel. task-3373836
This fixes an issue where opening certain Company document folders showed incorrect breadcrumbs and hid available actions. Users can now navigate these folders more reliably and access the expected options.
Original PR description
To reproduce: Open a non-pinned folder in "Company", the breadcrumb will not be correctly shown and actions are not available. When simply removed from the returned records, no item is added in the breadcrumbs on opening a non-pinned company root folder. Co-authored-by: Lopes Marc (loma) <loma@odoo.com> Task-4216195