Odoo Changelog — 2026-02-25

Wednesday, February 25, 2026

7 changes · saas-18.3

Bug Fixes(7)

Resolved issues and error corrections

[FIX] helpdesk_stock: helpdesk user should access ticket

Enterprisesaas-18.3helpdesk_stock

This update resolves an issue where helpdesk users with limited access were unable to view tickets due to a restriction on accessing related stock records. The fix adds a permission group to allow helpdesk users to read the necessary stock information, ensuring they can properly access and manage tickets.

Original PR description

To reproduce:
=============
- install helpdesk_stock
- with user having only User rights on helpdesk and nothing on other modules
- try to access a ticket -> AccessError

Problem:
========
when reading the ticket, the field `suitable_product_ids` is computed, and it requires read access to records the user doesn't have access to, which raises an AccessError.

Solution:
=========
Add the group `stock.group_stock_user` to the field, so that only users having access can read it.

backport of https://github.com/odoo/enterprise/pull/59605

opw-5907657

Forward-Port-Of: odoo/enterprise#108139
Forward-Port-Of: odoo/enterprise#107291

#helpdesk#stock#access

[FIX] account: allow child companies to use parent contacts

PR #250271

Coresaas-18.3accountMedium

This update allows branch companies to correctly see and use contacts belonging to their parent company when creating invoices or vendor bills. Previously, a branch company couldn't access these contacts due to a technical restriction. This fix ensures seamless multi-company operations.

Original PR description

Currently, when operating in a branch company, contacts belonging to the parent company are not visible in the partner dropdown on Invoices or Vendor Bills. ### **Steps to reproduce:** 1) Create a…

Currently, when operating in a branch company, contacts belonging to the parent company are not visible in the partner dropdown on Invoices or Vendor Bills.

### **Steps to reproduce:**
1) Create a multi-company hierarchy (Company A -> Branch B). 
2) Create a contact owned by Company A.
3) Switch the current company to Branch B.
4) Go to Accounting > Customers > Invoices and create a new invoice.
5) Try to select the contact created in step 2.

### **Current/Buggy Behavior:**
The contact does not appear in the search results.

### **Expected Behavior:**
The contact should be selectable.

### **Root Cause:**
since commit https://github.com/odoo/odoo/commit/67169c42061cb51bc68f6c74f0674a670dd04f58,
the partner model supports the standard
`check_company=True` mechanism, and record rules were updated to allow
branches to access partners of their parent company.

However, the `partner_id` field on the `account.move` form view still
retained a explicit domain: `[('company_id', 'in', (False,
company_id))]` as shown at [1].

This domain overrides the standard `check_company` behavior.
due to which it restricts the selection to partners owned by the current company
(the branch) or partners with no company set. It explicitly excludes
partners owned by the parent company.

### **Fix:**
Remove the domain at [1],
This allows the field to rely on the standard `check_company=True`
logic, which correctly handles the multi-company hierarchy and allows
branches to select parent company partners.

[1]- https://github.com/odoo/odoo/blob/6b7b83449739932aa8420ef8fcd888116e3c0f8a/addons/account/views/account_move_views.xml#L896

**opw-5484611**

Forward-Port-Of: odoo/odoo#244671

[FIX] point_of_sale: correct POS receipt tax label after fiscal position

PR #249697

Coresaas-18.3point_of_sale

This update fixes an issue where POS receipts incorrectly showed the standard 21% tax label, even when a fiscal position (like 6%) was applied. The fix ensures that the POS receipt accurately reflects the tax rate based on the selected fiscal position, improving accuracy and compliance.

Original PR description

Steps:

- Install l10n_be_pos_restaurant.
- Create a restaurant POS configuration with presets.
- Assign a fiscal position to one preset that replaces 21% tax with 6%.
- Open a POS session and process an order using that preset.

Issue:

- The POS receipt still displays the 21% tax's tax group label, even though the 6% tax is correctly applied.

Cause:

- Fiscal position was not taken into account when computing the tax group label for POS receipt orderlines.

Fix:

- Apply the fiscal position when determining the POS receipt tax group label.

Task-5899938

Forward-Port-Of: odoo/odoo#248571

#pos#tax#fiscal_position

[FIX] l10n_es_reports: make 'BOE' button of reports branch_allowed

PR #107252

Enterprisesaas-18.3l10n_es_reportsMedium

This update resolves an issue preventing the export of BOE reports when using multi-company mode with companies having different VATs. The fix ensures the report options correctly recognize all branch companies, allowing users to proceed with the export functionality. This improves the reliability of tax reporting.

Original PR description

**Steps to reproduce:**
* Install the **l10n_es_reports** module.
* Create a parent company with two branch companies with all has different VATs.
* Enable **multi-company mode** with all companies selected.
* Go to tax report `Mod 390`
* From gear icon clck on `BOE`.

**Observed behavior:**
* A warning appears: Please select the main company and its branches in the company selector to proceed.
* Not able to export BOE.

**Cause:**
* This is because the tax report's options only consider one of the two companies (because they have different VAT numbers). The button is not declared as branch_allowed, so when clicked, it checks whether all the companies of the branch hierachy are in the options => they're not => error.

**Fix:**
* Added the `'branch_allowed': True` to the `BOE` button options.

opw-5891472

#reporting#vat#multi-company

[FIX] website_sale: product_published_with_category tour

PR #250429

Coresaas-18.3website_sale

This update resolves an issue where products weren't automatically marked as 'published' when assigned to a category in the product editor. The fix ensures that category assignments correctly update the product's visibility status, preventing products from being incorrectly hidden. This improves the user experience and data accuracy.

Original PR description

Error:
AssertionError: False is not true
self.assertTrue(product.website_published)

Cause:
Commit https://github.com/odoo/odoo/commit/ca198cfc7c41a8c15b2734518016007aa1c16457 relies on _onchange_public_categ_ids to set
website_published=True when a category is assigned. Two issues:
1. website_published was not in the dialog form view, so its onchange
   value was never tracked or sent to the server on save.
2. The tour clicks Save before the onchange response is received,
   so the product is saved without website_published=True.

Fix:
- Add website_published as an invisible field in the dialog form view
  so its value is tracked and sent on save.
- Wait for the category badge to appear before submitting, ensuring
  the onchange has completed before save.

runbot-237976

Forward-Port-Of: odoo/odoo#249027

#website#product#category#visibility

[FIX] l10n_ae_hr_payroll: fix rate per hour for attendance based contract

PR #108628

Enterprisesaas-18.3l10n_ae_hr_payrollMedium

This update fixes an issue where salary calculations for employees on attendance-based contracts were incorrect. The system now accurately determines hourly rates for various allowances by using the employee's planned working schedule instead of their recorded attendance hours, ensuring accurate payroll processing for this contract type.

Original PR description

Step to Reproduce:
- install UAE Payroll localization and attendance
- create employee and running employee contract and give basic salary, housing, transportation and other allowance.
- work entry source should be attendance
- create a payslip and compute sheet.

Issue:
- The values for payslip lines are not as expected.
- The rate per hour for basic salary , housing, transportation and other allowances was being calculated based on employee's attendance work entries, not the planned working schedule.

Reason:
- When using attendance-based contracts, the hourly rates for basic salary, housing, transportation, and other allowances should be calculated based on the working schedule's hours per day, if a working schedule is available.

Solution:
- Instead of sum_worked_hours which takes working hours of employee's work entries, use total_number_of_days multiplied by the hours per day from the working schedule.

task-5270185

Forward-Port-Of: odoo/enterprise#103282

#payroll#attendance

[FIX] base: correct Qatar currency label

PR #250466

Coresaas-18.3basel10n_qaaccount

This update fixes a labeling error in Odoo invoices for Qatar. Previously, the invoice amount description incorrectly used 'Rial'. This change ensures the correct 'Riyal' terminology is displayed, aligning with local accounting standards and improving accuracy for users in Qatar.

Original PR description

Steps to reproduce:
1- Install Accounting and 'l10n_qa' modules
2- Switch to Qatar company and enable "Total amount of invoice in letters" under accounting settings
3. Issue an invoice and preview it

The issue:
The description of the amount uses "Rial"

Expected behavior:
The amount should use "Riyal"

opw-5919587

Forward-Port-Of: odoo/odoo#250299

#currency#accounting#Qatar

To reproduce: ============= - install helpdesk_stock - with user having only User rights on helpdesk and nothing on other modules - try to access a ticket -> AccessError Problem: ======== when reading the ticket, the field `suitable_product_ids` is computed, and it requires read access to records the user doesn't have access to, which raises an AccessError. Solution: ========= Add the group `stock.group_stock_user` to the field, so that only users having access can read it. backport of https://github.com/odoo/enterprise/pull/59605 opw-5907657 Forward-Port-Of: odoo/enterprise#108139 Forward-Port-Of: odoo/enterprise#107291

Currently, when operating in a branch company, contacts belonging to the parent company are not visible in the partner dropdown on Invoices or Vendor Bills. ### **Steps to reproduce:** 1) Create a multi-company hierarchy (Company A -> Branch B). 2) Create a contact owned by Company A. 3) Switch the current company to Branch B. 4) Go to Accounting > Customers > Invoices and create a new invoice. 5) Try to select the contact created in step 2. ### **Current/Buggy Behavior:** The contact does not appear in the search results. ### **Expected Behavior:** The contact should be selectable. ### **Root Cause:** since commit https://github.com/odoo/odoo/commit/67169c42061cb51bc68f6c74f0674a670dd04f58, the partner model supports the standard `check_company=True` mechanism, and record rules were updated to allow branches to access partners of their parent company. However, the `partner_id` field on the `account.move` form view still retained a explicit domain: `[('company_id', 'in', (False, company_id))]` as shown at [1]. This domain overrides the standard `check_company` behavior. due to which it restricts the selection to partners owned by the current company (the branch) or partners with no company set. It explicitly excludes partners owned by the parent company. ### **Fix:** Remove the domain at [1], This allows the field to rely on the standard `check_company=True` logic, which correctly handles the multi-company hierarchy and allows branches to select parent company partners. [1]- https://github.com/odoo/odoo/blob/6b7b83449739932aa8420ef8fcd888116e3c0f8a/addons/account/views/account_move_views.xml#L896 **opw-5484611** Forward-Port-Of: odoo/odoo#244671

Steps: - Install l10n_be_pos_restaurant. - Create a restaurant POS configuration with presets. - Assign a fiscal position to one preset that replaces 21% tax with 6%. - Open a POS session and process an order using that preset. Issue: - The POS receipt still displays the 21% tax's tax group label, even though the 6% tax is correctly applied. Cause: - Fiscal position was not taken into account when computing the tax group label for POS receipt orderlines. Fix: - Apply the fiscal position when determining the POS receipt tax group label. Task-5899938 Forward-Port-Of: odoo/odoo#248571

**Steps to reproduce:** * Install the **l10n_es_reports** module. * Create a parent company with two branch companies with all has different VATs. * Enable **multi-company mode** with all companies selected. * Go to tax report `Mod 390` * From gear icon clck on `BOE`. **Observed behavior:** * A warning appears: Please select the main company and its branches in the company selector to proceed. * Not able to export BOE. **Cause:** * This is because the tax report's options only consider one of the two companies (because they have different VAT numbers). The button is not declared as branch_allowed, so when clicked, it checks whether all the companies of the branch hierachy are in the options => they're not => error. **Fix:** * Added the `'branch_allowed': True` to the `BOE` button options. opw-5891472

Error: AssertionError: False is not true self.assertTrue(product.website_published) Cause: Commit https://github.com/odoo/odoo/commit/ca198cfc7c41a8c15b2734518016007aa1c16457 relies on _onchange_public_categ_ids to set website_published=True when a category is assigned. Two issues: 1. website_published was not in the dialog form view, so its onchange value was never tracked or sent to the server on save. 2. The tour clicks Save before the onchange response is received, so the product is saved without website_published=True. Fix: - Add website_published as an invisible field in the dialog form view so its value is tracked and sent on save. - Wait for the category badge to appear before submitting, ensuring the onchange has completed before save. runbot-237976 Forward-Port-Of: odoo/odoo#249027

Step to Reproduce: - install UAE Payroll localization and attendance - create employee and running employee contract and give basic salary, housing, transportation and other allowance. - work entry source should be attendance - create a payslip and compute sheet. Issue: - The values for payslip lines are not as expected. - The rate per hour for basic salary , housing, transportation and other allowances was being calculated based on employee's attendance work entries, not the planned working schedule. Reason: - When using attendance-based contracts, the hourly rates for basic salary, housing, transportation, and other allowances should be calculated based on the working schedule's hours per day, if a working schedule is available. Solution: - Instead of sum_worked_hours which takes working hours of employee's work entries, use total_number_of_days multiplied by the hours per day from the working schedule. task-5270185 Forward-Port-Of: odoo/enterprise#103282

Steps to reproduce: 1- Install Accounting and 'l10n_qa' modules 2- Switch to Qatar company and enable "Total amount of invoice in letters" under accounting settings 3. Issue an invoice and preview it The issue: The description of the amount uses "Rial" Expected behavior: The amount should use "Riyal" opw-5919587 Forward-Port-Of: odoo/odoo#250299