Odoo Changelog — 2025-12-26

Friday, December 26, 2025

8 changes · 18.0

Improvements(1)

Enhancements to existing features

Odoo19 ee

Enterprise18.0crmsaleMEDIUM

This update automatically assigns newly created leads to the sales team's leader if the ticket's responsible user isn't already a salesperson within the team. This ensures leads aren't missed due to a lack of automatic assignment rules, improving lead follow-up efficiency.

#crm#lead#sales

Bug Fixes(7)

Resolved issues and error corrections

[FIX] account_payment: wip

PR #240501

Core18.0account_paymentMEDIUM

This update fixes a bug preventing credit card payment journals from being selectable in the payment provider setup. Previously, only bank journals were displayed, limiting payment options. The change expands the journal domain to include credit card journals, ensuring full compatibility and functionality.

Original PR description

Steps to reproduce:
1. Install account_payment.
2. Go to Payment Providers and install the demo provider.
3. Create a journal with type Credit Card.
4. Open Payment Provider → Demo → Under Payment Follow-up.
5. Try to select a payment journal.

Issue:
Only journals of type Bank are displayed.
Journals with type Credit Card are not selectable in the payment provider.

Cause:
Since credit card journals share the same posting behavior as bank journals for payments, they should also be allowed. Credit card journals were not selectable in payment providers because the journal domain was restricted to journals of type bank, excluding credit journals.

Solution:
Extend the journal domain to include journals of type credit, allowing credit card journals to be selected in payment providers.

opw-5411748

#payments#accounting#credit card

[FIX] product,sale: ensure cart quantity updates correctly

PR #241411

Core18.0productsaleMEDIUM

This update fixes an issue where the cart didn't accurately reflect changes to product quantities. The fix replaces a delayed update mechanism with immediate updates when a user modifies the quantity field, ensuring correct cart calculations and a smoother checkout experience. This improves the reliability of the shopping cart functionality.

Original PR description

**Steps to produce:** - Install `website_sale` with demo data. - Go to the shop page. - Select product `Customizable Desk` > click `Add to cart`. - In the wizard, change the quantity to 100 and…

**Steps to produce:**
- Install `website_sale` with demo data.
- Go to the shop page.
- Select product `Customizable Desk` > click `Add to cart`.
- In the wizard, change the quantity to 100 and directly click `Checkout`.

**Issue:**
- The cart shows the product with quantity = 1 instead of the edited value.

**Root Cause:**
- The template uses `t-on-change`, which only triggers when the input
  loses focus or is explicitly modified.
- When the user clicks `Checkout`, both `setQuantity` and `onConfirm`
  are executed in parallel.
- If `onConfirm` runs first, it reads the previously stored quantity
  (`1` from `this.state.products` initialized in `onWillStart`) before
  `setQuantity` has updated the value.
- Consequently, the checkout process proceeds with the stale quantity
  instead of the newly entered one.

**Solution:**
- Replace `t-on-change` with `t-on-input` so that the quantity is updated immediately when the user edits the field.
- This ensures the correct quantity is reflected in the cart even if the user proceeds directly to checkout.

opw-5435672
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#cart#checkout#quantity

[FIX] industry_fsm_stock: ensure cart quantity updates correctly

PR #102925

Enterprise18.0industry_fsm_stock

This update fixes an issue where the cart didn't accurately reflect quantity changes made within the Field Service module. The fix replaces a trigger mechanism that only updated quantities after losing focus, ensuring the correct quantity is displayed immediately after editing. This improves the user experience and prevents order discrepancies.

Original PR description

**Steps to produce:**
- Install `industry_fsm_stock` with demo data.
- Open any task in the field service module.
- Click on the Products icon on top > Click on `Customizable Desk`.
- Change the quantity to 100 and directly go back.

**Issue:**
- The cart shows the product with quantity = 1 instead of the edited value.

**Root cause:**
- The template used `t-on-change`, which only triggers when the HTML input loses focus or changes via another interaction.
- In this case, clicking "Checkout" directly does not trigger the onchange event, so the updated quantity is ignored.

**Solution:**
- Replace `t-on-change` with `t-on-input` so that the quantity is updated immediately when the user edits the field.
- This ensures the correct quantity is reflected in the cart even if the user proceeds directly to checkout.

opw-5435672
---

#field service#cart#quantity

[FIX] account_batch_payment: Add sudo for non hr users

PR #102875

Enterprise18.0account_batch_payment

This update enhances security by ensuring that the process of checking employee addresses during batch payments is accessible to all users, regardless of their HR group affiliation. Previously, restricted access limited functionality. This change adds sudo access to a specific function to ensure broader access without compromising data security.

Original PR description

In commit a6ed1bd, new logic for handling employee addresses was introduced. However, the _get_all_addr function requires employee_ids, which implicitly requires access to the Employees model and, therefore, be in HR groups.

During the compute process, _get_all_addr is only used to check whether an employee has an address; no address data is exposed.

To fix this issue, the call to _get_all_addr should be executed with sudo().

OPW-5428523

Forward-Port-Of: odoo/enterprise#102851

#access control#security#batch payments

[FIX] account_edi_ubl_cii: add invoice date to test invoices

PR #240957

Core18.0account_edi_ubl_cii

This update corrects a bug in the account_edi_ubl_cii module's test invoices. The missing invoice date previously caused incorrect tax calculations. Adding the date ensures accurate tax application during testing, preventing potential issues with fiscal positions.

Original PR description

When merging odoo/odoo#236692, the invoice date was missing on the test invoices. This could lead to issues when there's no qualifying fiscal position. Adding it removes the need to recompute the fiscal position ensuring the correct taxes are applied for the relevant test case.

No task ID

#account#tax#testing

[FIX] pos_urban_piper: update product description while re-syncing menu

PR #102846

Enterprise18.0pos_urban_piperMEDIUM

This update ensures that changes to product descriptions in Odoo are now correctly reflected in the UrbanPiper system during menu synchronization. Previously, updates to product descriptions weren't consistently propagated, leading to outdated information. This fix improves data accuracy and consistency between Odoo and UrbanPiper.

Original PR description

Before this commit:
---
When we sync the menu with the product description and later update the product description, re-syncing the menu does not update the product description in UrbanPiper.

After this commit:
---
This fix ensures that any change in the product description is properly sent to UrbanPiper during menu synchronization.

task-5439271

#urbanpiper#menu sync#product description

[FIX] website: Search suggestions hidden in grid layout snippets

PR #239607

Core18.0web_editor

This update fixes an issue where search suggestions were hidden behind product categories when using the grid layout in the website builder. The fix ensures that search suggestions are always visible, improving the user experience when searching for products within grid-based layouts. This resolves a visual inconsistency and ensures proper functionality.

Original PR description

Steps to reproduce:
===================
-  Add a product categories block with a search bar in the inner content of the block, like "s_product_list".
- Drag a "Search" snippet inside of the block in top of products categories
- Change the layout to "Grid" & Save.
- Type in the search bar to trigger autocomplete suggestions. -> The suggestions appear behind the product categories and are not visible.

Cause:
======
When a searchbar snippet is placed inside a section using grid mode, the autocomplete dropdown was hidden behind sibling grid items. This occurred because the grid layout applies inline z-index to each column (via `_placeColumns` `in grid_layout_utils.js` (See [1])), creating stacking contexts that trapped the dropdown.
So once you change to grid mode layout `_toggleGridMode` function will be triggered which will call  `_placeColumns` that will assign z-index; (See [2])

Solution:
=========
Override the inline z-index on grid items containing a searchbar

[1]: https://github.com/odoo/odoo/blob/d4411c27b469e5dcc526b5b1f8ea4498f2b08567/addons/web_editor/static/src/js/common/grid_layout_utils.js#L225

[2]: https://github.com/odoo/odoo/blob/d4411c27b469e5dcc526b5b1f8ea4498f2b08567/addons/web_editor/static/src/js/common/grid_layout_utils.js#L138

opw-5392011

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#website#search#grid layout

Steps to reproduce: 1. Install account_payment. 2. Go to Payment Providers and install the demo provider. 3. Create a journal with type Credit Card. 4. Open Payment Provider → Demo → Under Payment Follow-up. 5. Try to select a payment journal. Issue: Only journals of type Bank are displayed. Journals with type Credit Card are not selectable in the payment provider. Cause: Since credit card journals share the same posting behavior as bank journals for payments, they should also be allowed. Credit card journals were not selectable in payment providers because the journal domain was restricted to journals of type bank, excluding credit journals. Solution: Extend the journal domain to include journals of type credit, allowing credit card journals to be selected in payment providers. opw-5411748

**Steps to produce:** - Install `website_sale` with demo data. - Go to the shop page. - Select product `Customizable Desk` > click `Add to cart`. - In the wizard, change the quantity to 100 and directly click `Checkout`. **Issue:** - The cart shows the product with quantity = 1 instead of the edited value. **Root Cause:** - The template uses `t-on-change`, which only triggers when the input loses focus or is explicitly modified. - When the user clicks `Checkout`, both `setQuantity` and `onConfirm` are executed in parallel. - If `onConfirm` runs first, it reads the previously stored quantity (`1` from `this.state.products` initialized in `onWillStart`) before `setQuantity` has updated the value. - Consequently, the checkout process proceeds with the stale quantity instead of the newly entered one. **Solution:** - Replace `t-on-change` with `t-on-input` so that the quantity is updated immediately when the user edits the field. - This ensures the correct quantity is reflected in the cart even if the user proceeds directly to checkout. opw-5435672 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

**Steps to produce:** - Install `industry_fsm_stock` with demo data. - Open any task in the field service module. - Click on the Products icon on top > Click on `Customizable Desk`. - Change the quantity to 100 and directly go back. **Issue:** - The cart shows the product with quantity = 1 instead of the edited value. **Root cause:** - The template used `t-on-change`, which only triggers when the HTML input loses focus or changes via another interaction. - In this case, clicking "Checkout" directly does not trigger the onchange event, so the updated quantity is ignored. **Solution:** - Replace `t-on-change` with `t-on-input` so that the quantity is updated immediately when the user edits the field. - This ensures the correct quantity is reflected in the cart even if the user proceeds directly to checkout. opw-5435672 ---

In commit a6ed1bd, new logic for handling employee addresses was introduced. However, the _get_all_addr function requires employee_ids, which implicitly requires access to the Employees model and, therefore, be in HR groups. During the compute process, _get_all_addr is only used to check whether an employee has an address; no address data is exposed. To fix this issue, the call to _get_all_addr should be executed with sudo(). OPW-5428523 Forward-Port-Of: odoo/enterprise#102851

When merging odoo/odoo#236692, the invoice date was missing on the test invoices. This could lead to issues when there's no qualifying fiscal position. Adding it removes the need to recompute the fiscal position ensuring the correct taxes are applied for the relevant test case. No task ID

Before this commit: --- When we sync the menu with the product description and later update the product description, re-syncing the menu does not update the product description in UrbanPiper. After this commit: --- This fix ensures that any change in the product description is properly sent to UrbanPiper during menu synchronization. task-5439271

Steps to reproduce: =================== - Add a product categories block with a search bar in the inner content of the block, like "s_product_list". - Drag a "Search" snippet inside of the block in top of products categories - Change the layout to "Grid" & Save. - Type in the search bar to trigger autocomplete suggestions. -> The suggestions appear behind the product categories and are not visible. Cause: ====== When a searchbar snippet is placed inside a section using grid mode, the autocomplete dropdown was hidden behind sibling grid items. This occurred because the grid layout applies inline z-index to each column (via `_placeColumns` `in grid_layout_utils.js` (See [1])), creating stacking contexts that trapped the dropdown. So once you change to grid mode layout `_toggleGridMode` function will be triggered which will call `_placeColumns` that will assign z-index; (See [2]) Solution: ========= Override the inline z-index on grid items containing a searchbar [1]: https://github.com/odoo/odoo/blob/d4411c27b469e5dcc526b5b1f8ea4498f2b08567/addons/web_editor/static/src/js/common/grid_layout_utils.js#L225 [2]: https://github.com/odoo/odoo/blob/d4411c27b469e5dcc526b5b1f8ea4498f2b08567/addons/web_editor/static/src/js/common/grid_layout_utils.js#L138 opw-5392011 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr