Original PR description

**Steps to reproduce:**
* Install the **Accounting** and **l10n_mx** modules.
* Open any product form view.
* Navigate to the **Accounting** tab.
* In the *UNSPSC Category* field, start typing a numerical code such as **'10101500'**.

**Observed behavior:**
* No results are returned, even though the corresponding UNSPSC code exists in the database.

**Cause:**
* The `_search_display_name` method used an exact match (`=`) on the `code` field, preventing any partial or prefix-based lookup during user input.

**Fix:**
* Replace the exact-match domain on `code` with a partial match using `ilike`, allowing users to find UNSPSC codes by typing any part of the numerical sequence.

opw-5244705

Forward-Port-Of: odoo/enterprise#99651

Original PR description

Changing the currency on a journal triggers the compute of
inbound/outbound method lines, which clears the method lines before
reasign the default method lines. This leads to the loss of any
outstanding account set on the method lines.

Steps:

- Have a bank journal with outstanding accounts set on the payment
  method lines
- Change the currency (in our case, this is the bank sync that changed
  the currency of the journal)
-> Outstanding accounts are missing on the payment method lines,
   even if the accounts currency is the same as the journals or no
   currency is set on the accounts.

opw-5175794

Forward-Port-Of: odoo/odoo#234008

Original PR description

Before this commit:
=======================
The `whiteboard_pen` product had no assigned category, while the main POS configuration was limited to specific categories.
As a result, `whiteboard_pen` was not displayed on the product screen. When no products were loaded, special products like gift cards and e-wallets also not shown,showing the `Load Sample` button instead of products. This caused tour tests expecting gift cards on the screen to fail.

After this commit:
======================
Assigned the same product category to whiteboard_pen as used in the POS configuration. This ensures that the product appears on the product screen and special products like gift cards also load properly, preventing the tour test from failing.

Runbot Error: 233434, 233435

Forward-Port-Of: odoo/odoo#233563

Original PR description

### Steps to reproduce:

- Create a new Project task.
- Insert a Table of Contents (e.g., /tableofcontent).
- Insert a quote below it (e.g., /blockquote).
- Place the cursor at the start of the empty quote and press Backspace.
- The Table of Contents is removed.

### Desired behavior after PR is merged:

- Empty blockquote is converted into a base container when backspace is pressed.

task-5246130

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

Forward-Port-Of: odoo/odoo#235087

Original PR description

Steps to Reproduce:

- Create a link in the editor (e.g., "abc").
- Select all and change the font size from 14 to 80.
- Two empty tags are created before and after the formatted <span><a></a></span> with only FEFF Characters.
- Change the font size again (e.g., back to 14).
- Multiple empty tags remain in the DOM.

Description of the issue this PR addresses:

- In the removeFeffs method, FEFF characters are replaced with empty text nodes, which can lead to unwanted empty elements and empty text nodes being left in the DOM.

Desired behavior after PR is merged:

- Empty text nodes resulting from FEFF replacement are now properly removed, preventing leftover empty elements in the DOM.

task-5097770

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

Forward-Port-Of: odoo/odoo#233909

Original PR description

In the Peru UBL, adding a reference to a partner would cause an error from the OSE (code 3090). This was because the call to super in _get_partner_party_identification_vals_list would add the partner.ref as an ID, which is incorrect in the Peruvian context. Removed the call to super which did not bring any other information.

ticket-5193233

Forward-Port-Of: odoo/enterprise#100043

Original PR description

Bug:
In Belgium, after 30 calendar days of sick leave, all public holidays during the sick leaves are no longer paid. But here they were still being paid.

Cause:
The method that was checking what to do about public holidays was never seeing public holidays since they were already changed to their corresponding work entries at the work entry generation.

Fix:
Add the public holidays in the context and change the condition for checking if the current leave is actually from a public holiday or not.

Task: 3864585

Forward-Port-Of: odoo/enterprise#98496
Forward-Port-Of: odoo/enterprise#95178

Original PR description

Before this PR:
- Sending invoice/vendor bill to eTIMS would send null item codes if products
  weren't registered.
- `View Product(s)` button in validation messages opened standard product
  variant view with generic product fields instead of eTIMS-specific fields.
- When sending multiple invoices via batch processing, product registration used
  incorrect company context (in `self.env.company`) instead of the specific
  invoice's company, causing products to be registered to the wrong company's
  eTIMS system.

After this PR:
- Products are automatically registered with eTIMS before sending
  invoices/vendor bills.
- `View Product(s)` button now opens custom `l10n_ke_kra_product_tree` view
  with eTIMS-specific fields.
- Product registration now properly uses the invoice's company context
  (`move.company_id`) ensuring products are registered to the correct company's
  eTIMS system in multi-company scenarios.

Task-5039671

Forward-Port-Of: odoo/enterprise#93375

Original PR description

**Steps to reproduce:**
* Install the *Accounting* module.
* Create a customer invoice.
* Post the invoice.
* Click the *gear* icon → **Print** → **Export ZIP**.
* Observe that the  invoice opens a blank page.

**Issue:**
* Clicking **Export ZIP** on an unsent invoice opens a blank page.

**Cause:**
* The `account.move.send` model returns an empty dataset when the invoice is not sent,
 leading to an empty export result.

**Fix:**
* Add a condition to display **Export ZIP** only when the invoice has been sent.

---
opw-5245483

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

Original PR description

We have some reports with sections, like l10n_lu generic tax return.

Since account.return are born, when submitting the lu tax return, the periodicity is wrongly
computed, because of the self in `_init_options_return_periodicity` is the section report, not the main,
but the account.return.type is set with report_id = main report

Step to reproduce:
  With a LU company:
    1. Create a journal entry for a previous period
    2. Submit the tax return for the same period
    3. The amount shown is the amount of the current month

Solution: use options['sections_source_id'] to fetch the return_type instead of self.return_type_ids

opw-5163352

Forward-Port-Of: odoo/enterprise#100063

Original PR description

If you unregister a Nemhandel user, it won't ever be picked up by the user db. 
And trying to unregister by hand will give a traceback. 
This is due to mismatch between Exception types.





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

Forward-Port-Of: odoo/odoo#236670

Original PR description

### Issue:
In the SAFT report both the Customer and the Supplier have the same account.

### Cause:
In the XML there was probably a typo and both have `property_account_payable_id` as account.

### Solution:
For the `Customers` node, use `property_account_receivable_id`.

opw-5144009

Forward-Port-Of: odoo/enterprise#99196

Original PR description

Setting the src of an element to null triggers a GET HTTP request to /null. This is not the intended behavior; we want to reset the source so that it is not linked to any file, but the browser interprets it as an attempt to load a file called "null".

This commit fixes the problem by resetting the source using removeAttribute instead.

[Task-5349985](https://www.odoo.com/odoo/project/5778/tasks/5349985)

Forward-Port-Of: odoo/enterprise#100146

Original PR description

When using a composite report whose sections aren't used independently, enabling that filter on the composite report needs to enable it on their sections as well, else it won't show in the UI. This is the standard behavior for all report filters.

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

Forward-Port-Of: odoo/odoo#237003
Forward-Port-Of: odoo/odoo#236893

Original PR description

When using a composite report whose sections aren't used independently, enabling that filter on the composite report needs to enable it on their sections as well, else it won't show in the UI. This is the standard behavior for all report filters.

Forward-Port-Of: odoo/enterprise#100240
Forward-Port-Of: odoo/enterprise#100148

Original PR description

Version:
- saas-18.4

Steps to reproduce:
- Add multiple documents in sign app.
- Add sign item for user in first document and keep second document without any sign item.
- Try sign document.

Issue:
- The "Click to Start" navigator is not visible when signing.
- `postRender` runs for all documents and calls `checkSignItemsCompletion`, which then calls `updateDocumentsWithUnsignedItems(false)` for documents without sign items.
- This passes false to `controlNavigatorVisibility`, hiding the navigator even though the first document has unsigned items.

Solution:
- In `controlNavigatorVisibility`, instead of relying only on the `hasUnsignedItems` flag, check if the current document is unsigned and has sign items for the current signer before toggling the navigator.

Impact:
- The "Click to Start" navigator now appears correctly, helping users start the signing process smoothly.

task-5148722

Original PR description

**Version:**
- saas-18.4

**Steps to reproduce:**
- Install the Sign app
- Upload a PDF and add a strikethrough or multiline field
- Mark the field as readonly and mandatory
- Try to sign the document

**Issue:**
- The sign request cannot be validated if the strikethrough or multiline field is both readonly and mandatory.

**Solution:**
- For strikethrough fields: use "striked" instead of the item name "strikethrough"
to set the correct value when the strikethorugh field is constant.

- For multiline fields: when the field is constant, the value doesn’t come through element.value; instead, it’s in element.textContent, so we need to set the value there.

**Impact:**
- Users can now mark these fields as readonly and mandatory without blocking the validation of the sign request.

task-5098750

Original PR description

`team_id` might be used in filters to conditionally see related `sale.order` for a specific (or set of) sales teams. If the field isn't indexed, it's a Sequential Scan on `sale_order`, which can be a large table.

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

Forward-Port-Of: odoo/odoo#237116

Original PR description

Steps to reproduce:
-------------------
1. Install `account_reports`
2. Switch the user language to Arabic
3. Go to Accounting > Reporting > General Ledger
4. Click on the 3-dots  > Annotate
5. Create a new annotation

Issue:
------
A traceback occurs:
```python
psycopg2.errors.InvalidDatetimeFormat: invalid input syntax for type date: "٢٠٢٥-١١-٣٠"
LINE 1: ... '2025-11-14 07:05:06.400902', 2, '٢٠٢٥-١١-٣٠', ...
```

Cause:
------
In Arabic locale, Luxon formats dates using the Arabic numbering system,
which is not a valid date literal for PostgreSQL, leading to an invalid date syntax error.

Solution:
---------
Use the Latin numbering system (`latn`) when formatting the annotation date.

Ticket [link](https://www.odoo.com/odoo/project.task/5244656)
opw-5244656

Forward-Port-Of: odoo/enterprise#99493

Original PR description

## Issue:
The `TotalTaxesWithhold` field in the exported XML could be negative, causing FACE to reject the document.

## Cause:
A previous change (https://github.com/odoo/odoo/pull/229236) added `values['tax_amount_currency']` to `TotalTaxesWithhold` without converting it to a positive value: https://github.com/odoo/odoo/blob/88b7ee6d9d2a7fe96512da0a7eaf8efcf9020ee1/addons/l10n_es_edi_facturae/models/account_move.py#L449

## Steps to reproduce:
- Install `l10n_es_edi_facturae`
- With the ES company, create an invoice with a product and a withholding tax (e.g., 15% WHI)
- Confirm the invoice and Send (Facturae)
- Open the XML attached in the chatter
- Observe that `TotalTaxesWithhold` is negative

opw-5220205

Forward-Port-Of: odoo/odoo#235774

Original PR description

When the company is "tax included" for all taxes, after signing to eTims, the invoice report:
- shows the currency symbol twice for "Taxable Amount".
- The xpath for 'td_subtotal' is also doubled for no reason.
- The "Total" columns is always price excluded instead of being price included.

task_id: 5252530

Forward-Port-Of: odoo/enterprise#100050

Original PR description

This commit fix several issue in kanban mobile view:

  - When a folder has folders AND documents, there is a huge gap between the two because of the kanban ghost records.
  - In the 'Recent' folder, folders and documents doesn't take all width.
  - In the 'Recent' folder, we can't scroll to see all the documents.

Task-4963198

Forward-Port-Of: odoo/enterprise#100134
Forward-Port-Of: odoo/enterprise#90647

Original PR description

This change was part of 04a4403 and was accidentally removed during a recent forward port.


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

Forward-Port-Of: odoo/odoo#237264

Original PR description

__Current behavior before commit:__
In "Repeat pattern" mode, users can set the background image's width and height to 0px, which doesn't make sense. Additionally, clearing these input fields resets their values to 0px instead of reverting them to `auto`.

__Description of the fix:__
Make it possible to clear those fields by setting their default value to `null` and set the minimum value to 1 to prevent the image from disappearing.

__Steps to reproduce:__
1. On the website, drop a `s_cover` snippet
2. Set Background > Image > Position to "Repeat pattern"
3. Delete the content of the "Width" input

=> The background disappears.

task-5094899

Original PR description

**Issue:**
Timesheet entries linked to reversed invoices are uneditable.

**Steps to reproduce:**
 - Create a service product invoiced by timesheets, and create a project & task.
 - In Sales, create a new quotation with the product.
 - Confirm the quotation, click on the task, and create a timesheet entry.
 - Create an invoice from the quotation.
 - Confirm the invoice, add a credit note, and reverse the invoice.
 - Go to the reversed invoice and access the timesheet through recorded hours.

the timesheet entry is uneditable, even though the invoice is reversed.

opw-4633121

Forward-Port-Of: odoo/odoo#236601
Forward-Port-Of: odoo/odoo#201921

Original PR description

In the goal of fixing the batch payments with EPD in the bank rec widget, we discovered another bug that was preventing the batch payments to change their state to "reconciled". This was due to some compute not being triggered again when one of its dependences did change (during another compute).

task-4681366

Forward-Port-Of: odoo/odoo#223310
Forward-Port-Of: odoo/odoo#222303

Original PR description

In the bank reconciliation widget, it is now possible to have batch payments containing payments linked to only invoice_ids. Such batch payment, once mounted in the widget, should reflect the invoice or move amounts of its payments, and not only the payments amount.
In the case of a payment-invoice combo that's elligible for an early payment discount, the early payment discount should also be displayed in the widget.

Example:
Invoice of 1000$ with possible EPD of 2%. A payment (with no move) is done (paid in the "early" period) for 980$.
The payment is then put into a batch payment.
Once in the bank rec widget, when mounting the 980$ batch payment to a statement line of 980$, the widget should display it as a batch payment line of 1000$ and add another 20$ Early payment Discount line.

task-4681366

Forward-Port-Of: odoo/enterprise#92593
Forward-Port-Of: odoo/enterprise#83077

Original PR description

For an empty package the  `quant_tasks` function will be executed without restriction of scope and can potentially slow the user request intensly.
And if there is no quants in the package the tasks are not necessary.

After the unpacking of the quants they are not in the package anymore.
Causing the call to quant_tasks to be done on an empty recordset.

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

Forward-Port-Of: odoo/odoo#234370

Original PR description

This was initially allowed so that the user could edit the description on combo item lines (since both the product and description fields are displayed in a single column). However, users seem to abuse this (see https://github.com/odoo/odoo/pull/234090).

For information, the description can still be edited, but to do so, the user must first hide the `Product` and `Product variant` columns (which can be shown again after making the necessary changes).

Forward-Port-Of: odoo/odoo#237148
Forward-Port-Of: odoo/odoo#235547

Original PR description

…ible

https://github.com/odoo/odoo/pull/236037 ignores the properties field if we don't have access to the definition model at all. However, we should also check field groups to avoid crashing if the user cannot access the definition field because of group restrictions.

Forward-Port-Of: odoo/odoo#237166
Forward-Port-Of: odoo/odoo#236912

Original PR description

When replicating changes from one field to other occurences of the same field in the document, the `data-oe-many2one-id` was not copied (for many2one fields). Thus it could lead to showing incorrect values in the sidebar, or saving them.

This commit fixes that by adding a dispatch to handlers after the replication, and implementing a handler that copies the `data-oe-many2one-id` when needed.

Steps to reproduce:
- Open website builder on a blog post
- Enable the "Sidebar"
- Enable the "Author" in the sidebar
- Click on the second occurence of the name of the author in the page
- Change the "Contact" associated with the author of the post
- Click on the first occurence of the name of the author in the page
- Bug: the name of "Contact" is the old one
- Change the "Contact" to yet another one
- Save
- Bug: the author is not the last one selected

task-5252648

Original PR description

In cases of credit notes, the xml would not be validated by the FACe. This was caused by the field 'ReasonDescription', which can only be one of the proposed field.

We used to provide it in English when the available reasons are only in Spanish.

Also fixed CorrectionMethodDescription.

See https://www.facturae.gob.es/formato/Paginas/version-3-2.aspx for more documentation.

ticket-5184181

Took the opportunity to improve the reversal wizard : 
In the reversal wizard, two fields 'Reason' would be displayed.

Only kept the mandatory one and used it in place of the non-mandatory one.

Forward-Port-Of: odoo/odoo#236684

Original PR description

In this PR:
-  Added XML records to set the EC Sales List report menu item as active for some EU countries that previously required manual activation.

Task-4885725

Forward-Port-Of: odoo/enterprise#93939

Original PR description

## Versions
17.0+

## Issue
It is possible to return more products than what has been picked in Rental.

## Steps to reproduce
- Create a service product available for rent;
- Create a rental SO for any partner:
  - Add 5 units of the created service;
  - Confirm the SO;
  - Pickup 5;
  - Return 4;
  - Return 4;
  - Check the SOL containing 5 delivered products and 8 returned products.

opw-5259727

Forward-Port-Of: odoo/enterprise#100303
Forward-Port-Of: odoo/enterprise#100015

Original PR description

Two forward-port commits[^1],[^2] corrupted the POT files of these modules. They both resulted in missing `msgstr` entries causing the `msgmerge` in Weblate to fail.

This commit regenerates the POT files to fix the issue.

[^1]: https://github.com/odoo/odoo/commit/4e51a4a259bbb36dbbd7f6aa59ba30280f97cd89
[^2]: https://github.com/odoo/odoo/commit/f3286d792e17746d2330b5e06d5c5c8e01c52928

Forward-Port-Of: odoo/odoo#237308
Forward-Port-Of: odoo/odoo#237031