Tuesday, March 3, 2026
21 changes · saas-19.2
Enhancements to existing features
This update introduces a simpler way to run Odoo tests by allowing users to use the '-t' alias for the --test-tags command. This change streamlines the testing process and makes it more convenient for developers. It's a minor improvement that enhances developer workflow.
Original PR description
Backport of https://github.com/odoo/odoo/pull/234287 <img width="408" height="151" alt="image" src="https://github.com/user-attachments/assets/7f22826f-6887-432b-8baf-8a6778b9cadf" /> Forward-Port-Of: odoo/odoo#250283 Forward-Port-Of: odoo/odoo#249123
This update enhances the testing process by clarifying documentation related to specific error codes (E8502 and E8505). The changes provide clearer explanations and examples, ensuring consistent and accurate testing of Odoo's translations.
Original PR description
- Update documentation link for E8502. - Clarify why E8505 is in place and give an example. Forward-Port-Of: odoo/odoo#251444
Resolved issues and error corrections
This update resolves a test issue related to the websiteUrlPicker component. The test previously relied on a real delay, leading to unpredictable failures. Now, the test uses a controlled time advance to accurately simulate the debounce process, ensuring consistent and reliable test results.
Original PR description
Issue: The websiteUrlPicker input has a 250ms debounce. The test was relying on a real 250ms delay to wait it out, creating a race condition that caused non-deterministic failures. Fix: The test now uses `advanceTime()` to advance the time to past the debounce. runbot-[241087](https://runbot.odoo.com/odoo/runbot.build.error/241087) Forward-Port-Of: odoo/odoo#251199
This update fixes a visual inconsistency in the Discuss app's dark mode. The background colors of breadcrumbs and navbar buttons were previously mismatched compared to the control panel. This change ensures a more polished and professional user experience across all Odoo modules in dark mode.
Original PR description
The background color of navbar buttons and breadcrumbs in discuss app differed from that of control panel. This PR aligns and syncs these colors for a consistent UI. | Before | After | |--------|-------| |<img width="467" height="99" alt="image" src="https://github.com/user-attachments/assets/2def30f8-18aa-4399-a5d1-1cdc70b4cd81" /> |<img width="458" height="111" alt="image" src="https://github.com/user-attachments/assets/5578cd25-7686-4543-a8dc-3e0fe5aeb4fc" />| This PR contains backport of #217608 task-[4936733](https://www.odoo.com/odoo/project/1519/tasks/4936733) task-[5487197](https://www.odoo.com/odoo/project/1519/tasks/5487197) Forward-Port-Of: odoo/odoo#251360 Forward-Port-Of: odoo/odoo#250601
A technical issue preventing payrun creation for Hong Kong employees has been fixed. The update corrects a naming error that was causing errors during payrun generation, ensuring accurate payroll processing for our HK clients. This resolves a previous disruption to the payrun workflow.
Original PR description
In the big commit adding eMPF to the hk localization, a function was miss named and was causing an error when trying to create a payrun. Steps to reproduce: - Install belgian localization - Install HK localization - Select the belgian company - Create a payslip for a belgian employee (works fine) - Create a payrun and select the same employee from the list - Get an error In this commit we fix the naming of the function and everything goes back to working. Task: 5960503 Forward-Port-Of: odoo/enterprise#109196
This update fixes an issue where new tables on restaurants with multiple floors were assigned numbers based on the highest number across all floors, leading to potential conflicts. Now, new tables are assigned numbers based on the highest number on the current floor, simplifying table management and preventing numbering errors.
Original PR description
Before this commit: =================== When multiple floors exist, creating a new table assigns the next table number based on the maximum table number across all floors. After this commit: ================== When multiple floors exist, creating a new table assigns the next table number based on the maximum table number of the current floor. Task: 5888449 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#246975
This update adjusts the size of custom snippet titles within Mass Mailing to ensure they are easily readable. A recent update to the preview snippet selector required a change in font size for these titles. This fix maintains the original appearance of custom snippets at the new scale, improving user experience.
Original PR description
In Mass Mailing, users can save modified snippets as Custom Snippets, allowing for their later reuse. These snippets can be found in the Custom category. However, their title was too large. This is due to d2b56435736e8d507434c1378cb68fae23e8511f rescaling the preview snippet selector, allowing for better readability of each snippet's text from the selector. As the default builder font size for custom snippet titles was set for the previous scale (50px at 0.3 scale), it has to be halved to restore its previous appearance at the new scale (25px at 0.6 scale). task-5959033 Forward-Port-Of: odoo/odoo#250609
This update corrects a technical issue in the Hungarian tax audit export process. Previously, changes to invoice data were unintentionally saved to the database, causing potential errors. The fix ensures data is properly cleared from the cache before and after savepoints, preventing these unwanted database updates.
Original PR description
At the moment, the Hungarian tax audit export wizard's `action_export` creates a savepoint with `flush=False`. The intention of this savepoint is to roll back the changes to `l10n_hu_edi_invoice_chain` once the savepoint exits. But because the changes to `l10n_hu_edi_invoice_chain` stay in cache, and the cache is not flushed before the savepoint is created nor cleared afterwards, those changes end up being committed to DB. Which is precisely what the savepoint was there to prevent. Solution: we use `flush=True` to make sure the cache is flushed before and cleared after the savepoint. task-none Forward-Port-Of: odoo/odoo#251322 Forward-Port-Of: odoo/odoo#250971
This update fixes a display issue in the website editor where an incorrect 'Custom URL' field was appearing. The change prevents this field from showing when the website URL doesn't support customization, ensuring a cleaner and more accurate SEO experience for users. This improves the usability of the website editor.
Original PR description
This PR hides the "Custom Url" field in the "Search Engine Optimization" when the URL of the current page do not contain any editable slug. Previously, this field could be filled when the URL did not…
This PR hides the "Custom Url" field in the "Search Engine Optimization" when the URL of the current page do not contain any editable slug. Previously, this field could be filled when the URL did not contain any modifiable slug. However, the value was not take into account since the route of the page did not expect slug. Reproduce: With an admin user, activate the website editor on an appointment page. Clicking on "Optimize SEO" in the "Site" dropdown menu, a form containing the "Cutsom Url" field is displayed. This field should represent the current page's URL but with fillable field instead of the editable URL part. In this case, this is not correct as the URL is repeated before and after the fillable field, which does not represent the current URL. Also, the URL is not modified with the value entered in the fillable field. After the fix: The "Custom Url" field must not be displayed when URL does not contain a customisable slug. Task-5114394 Forward-Port-Of: odoo/odoo#251294 Forward-Port-Of: odoo/odoo#231609
A recent update to the Document linking dialog caused a minor error when users tried to add documents via the command palette. This fix updates a key part of the software's code to correctly identify the 'Add as link(s)' button, ensuring the dialog functions as intended. This resolves a display issue and improves the user experience.
Original PR description
How to reproduce: Open any record, go to the Activity, select Document, then type “/File” in the command palette and click it. An error is raised. Issue: The xpath expression `contains(., 'Paste Link')` cannot locate the element because the button label was renamed to `Add as link(s)` in commit a4ca17329d7c21be487a53c5e0b9afa39e6dad3a. Resolution: Update the xpath to correctly target the new button definition `Add as link(s)` instead of the old label, preventing the element lookup failure and restoring proper dialog rendering. Task-5946396
This update resolves an issue where archived employees were still visible in the attendance Gantt view. The change ensures that only currently active employees are displayed, improving the accuracy and clarity of the attendance reporting tool. This prevents confusion and outdated information.
Original PR description
Steps to reproduce: 1. install `hr_attendance_gantt` 2. create an employee 3. make attendance records for the employee in the previous months 4. archive the employee When opening the gantt view of the attendance, a row appears for the archived employee, with no attendance showing up. This commit adds a constraint to only show the active employees. opw-5490119 Forward-Port-Of: odoo/enterprise#107972 Forward-Port-Of: odoo/enterprise#106486
This update resolves an issue where a security check was incorrectly performed on multiple records within the account module. The fix ensures the check is now executed only once, strengthening the system's security posture. This change improves the reliability and efficiency of user trust validation.
Original PR description
In some cases, the check was done on multiple records, though the method should be called on one and only one record. Forward-Port-Of: odoo/odoo#251589 Forward-Port-Of: odoo/odoo#251457
This update corrects a display issue where vendor product names and codes were appearing twice in the purchase receipt descriptions. The root cause was a redundant addition of vendor information during the receipt generation process. This change ensures accurate and consistent product descriptions in purchase receipts.
Original PR description
Version : saas-18.4+e Steps to reproduce ------------------ Create a product and add a line in the purchase tab with a “Vendor Product Name” and/or a “Vendor Product Code”. Create a purchase order…
Version : saas-18.4+e Steps to reproduce ------------------ Create a product and add a line in the purchase tab with a “Vendor Product Name” and/or a “Vendor Product Code”. Create a purchase order for this product with the right vendor and confirm it. Go to the delivery receipt, the vendor code and/or name are added twice in the description. Why is it happening ------------------ The _compute_description_picking method from stock.move, which is overridden in purchase_stock module, adds the vendor code and name to the description. However, if no description_picking has been set on the product, the description is already defined as the vendor code and name. Solution ------------------ I propose to remove the code and the name from the vendor_reference variable if the original description already contains them. opw-5392855 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#251337 Forward-Port-Of: odoo/odoo#242075
This update fixes a JavaScript error that occurred when users closed the signing certificate wizard without saving. The fix ensures the system correctly handles wizard dismissals, preventing a crash and improving stability. This resolves a potential disruption for users completing the certificate signing process.
Original PR description
**Issue:**
Closing the signing certificate wizard without saving triggers a client-side traceback (`UncaughtPromiseError: Invalid ids list: [object Object]`).
**Cause:**
When the wizard dialog is discarded, Odoo's dialog manager passes a dismissal object (`{dismiss: true}`) to the `onClose` callback. The existing code only checked if the payload was truthy (`if (cert_id)`), causing it to attempt to update the `signing_certificate_id` Many2one field with the event object. The framework's validation (`validatePrimitiveList`) expects an integer or array of integers, resulting in a crash when it tries to parse the object.
**Fix:**
Updated the `onClose` callback to strictly verify the type of the payload (`typeof cert_id === 'number'`). The record is now only updated when the wizard successfully returns a valid primitive integer ID.
task: 5975643
Forward-Port-Of: odoo/enterprise#108864This update fixes an issue where the VAT exigibility mention was incorrectly shown on French invoices. The change ensures that the mention is only displayed when required by French tax regulations – specifically, when a service VAT uses invoice-based tax exigibility. This ensures compliance and accurate invoice presentation.
Original PR description
The VAT exigibility mention on French invoices was incorrectly displayed. - For goods, VAT on debits is the default regime, therefore the mention is not mandatory and must not be shown. - For services, VAT is normally due on payment. The mention “TVA payée sur les débits” must be displayed only when a service VAT uses tax exigibility based on invoice. This commit updates the logic to display the mention only in this specific case and omits it otherwise. Task:5418502 Forward-Port-Of: odoo/odoo#248588
This update fixes a visual issue with the API documentation tooltips, ensuring they display correctly and consistently. The changes align the text, improve how tooltips are hidden, and prevent empty tooltip content from appearing, resulting in a cleaner and more reliable user experience for developers.
Original PR description
In api_doc, the method parameters tooltips were broken. This commit fixes them by: - aligning the text to the left - improving the hideTooltip behavior - preventing `undefined` tooltip content from being displayed task-5246075 Forward-Port-Of: odoo/odoo#248289
This update fixes a visual issue where group names in list views were being cropped due to incorrect column spanning. The change ensures group names have sufficient space, regardless of the list's content, improving readability and the overall user experience. This resolves a minor aesthetic problem that could have impacted how users viewed grouped data.
Original PR description
Have a grouped list view with no aggregate fields. Before this commit, the colspan of the first `th` in group header rows wasn't optimally computed. These `th` can span to the very last cell…
Have a grouped list view with no aggregate fields. Before this commit, the colspan of the first `th` in group header rows wasn't optimally computed. These `th` can span to the very last cell (excluded), which may contain a cog menu. However, they only spanned to the second to last cell. As a consequence, in a list with only 2 columns, e.g. a handle and a name, the groups' name only got a few px available, and were hence cropped. The issue came from successive reworks of the group header row, leading to the pager being finally moved from its own column (after the last aggregate column), to the group name cell (with ms-auto). The logic is easier now, as a group header row looks like this: - a single `<th colspan="n">` (n >= 1) to display the group name: spans to the first aggregate column excluded or to the last cell excluded if no aggregate (colspan + 1 if rows have selectors) - one `<th colspan="1">` for each aggregate column - optionally one `<th colspan="m">` (m >= 1) for all columns after the last aggregate column - a single `<th colspan="1">` for the potential cog menu (optional dropdown column) opw~5730396 Before <img width="1918" height="471" alt="image" src="https://github.com/user-attachments/assets/8f55322b-1603-42cc-a48b-a2010ff12e25" /> After <img width="1909" height="423" alt="image" src="https://github.com/user-attachments/assets/0bca4865-88a1-424d-a1af-1523dbfa911c" /> Forward-Port-Of: odoo/odoo#251411
This update corrects a bug where the invoice section was disappearing when the product price was hidden. The fix also resolves a related issue where removing tax caused a duplication of the invoice subsection. This ensures invoices are correctly rendered in previews and PDFs, providing accurate financial information.
Original PR description
**STEP TO REPRODUCE** 1. Create an invoice, with: - Section A - Subsection 1 - product a, with tax Click on hide price on section A, and preview the invoice. Notice the Section A is missing from the preview/pdf. If you remove the tax on product a, there will also be a bug where Subsection 1 is duplicated, with one copy with no children lines below it. opw-5927563 Forward-Port-Of: odoo/odoo#251344 Forward-Port-Of: odoo/odoo#249808
This update fixes an issue where Point of Sale session messages were consistently displayed in English, regardless of the user's selected language. The fix ensures that all cash-related messages within POS sessions are now translated accurately based on the user's language preference, improving the user experience for international customers.
Original PR description
**Problem:** When opening or closing a POS session, chatter messages display untranslated English text regardless of the user's language setting. **Steps to reproduce:** 1. Set user language to any non-English language (e.g., Spanish) 2. Open a POS session and register cash in/out operations 3. Close the session 4. Check the chatter messages - labels appear in English **Current behavior:** Messages display in English: "Opening cash difference", "Opening cash expected", "Opening cash counted", "Closing difference", etc. **Expected behavior:** Messages should be translated according to the user's language setting. **Cause of the issue:** The hardcoded strings were not wrapped in the translation function `_()`, preventing them from being translated. **Fix:** Wrap the concatenated strings with `_()` to enable proper translation of all cash details messages. opw-5185310 Forward-Port-Of: odoo/odoo#248982 Forward-Port-Of: odoo/odoo#244501
This update resolves a technical issue where the new booking view for POS appointments was interfering with other modules. By restricting the view's usage to the POS system, this fix ensures compatibility and prevents disruptions to other parts of the Odoo platform. This improves stability and prevents potential conflicts.
Original PR description
The list view in pos appointment would replace the original list view on calendar event and break other modules. This PR will add the `primary` mode for the new view so it is only used inside the POS Runbot Error: [234914](https://runbot.odoo.com/odoo/runbot.build.error/234914) Forward-Port-Of: odoo/enterprise#107132
This update fixes an issue where newly hired employees were incorrectly receiving their private email address as their work email. The fix clears the employee's work_email field during the contract signing process, ensuring it reflects the correct work email from the salary configurator. This prevents confusion and ensures accurate employee record information.
Original PR description
**Steps to Reproduce:** 1. Send an offer to an applicant. 2. The applicant submits their details via the salary configurator and enters their private email in the Email field. 3. Once the offer and contract are signed, an employee record is created in Odoo. 4. In the created employee record, the `work_email` field is populated with the email entered in the salary configurator. This same value is also present in `private_email`, which is correct. **Reason:** - The email entered in the salary configurator is stored on the partner and represents the applicant's private email. - The employee's `work_email` field is linked to the partner's email via compute and inverse methods, causing it to inherit the private email value when the employee record is created. **Solution:** - Explicitly clear the employee's work_email field when the applicant sign. task: 5502797 Forward-Port-Of: odoo/enterprise#109074 Forward-Port-Of: odoo/enterprise#106974