**Description of the issue/feature this PR addresses:**
----------------------------------------------
When editing messages or log notes from the Chatter, users are limited to
the inline composer and cannot switch to the full composer. This restricts
their ability to perform advanced editing (rich formatting, attachments,
mentions handling, etc.) once edit mode is initiated.


**Current behavior before PR:**
----------------------------------------------
- No option is available to open the full composer while editing
- Users must either continue with limited inline editing or discard changes
- Full composer can only be used when creating new messages, not editing existing ones


**Desired behavior after PR is merged:**
----------------------------------------------
- "Open Full Composer" action is available while editing messages/notes
- Full composer opens with existing message content pre-filled
- Attachments, mentions, and formatting are preserved during transition
- Saving from full composer updates the original message instead of creating a new one
- Existing behavior for new messages remains unchanged

Related Enterprise PR: https://github.com/odoo/enterprise/pull/126622

Task-6015654

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

Description
-----------
Creating or updating stock move lines calls `_create_check()` to find the quality control points applicable to each detailed operation.

Category-scoped points previously searched for products once per quality point and category. The method then performed another `quality. point` search for every move line, although those point ids came from the recordset fetched at the beginning of the method.

This commit resolves all category-scoped products in one search and reuse the already-fetched quality points.

Benchmark
---------
```xml
<?xml version="1.0" encoding="utf-8"?>
<odoo>
    <!--
        Reproduces the two query-scaling paths in stock.move.line._create_check:
        category-scoped control points and a large batched move-line creation.

        The final job is the benchmark target. With the former implementation,
        its query count grew with both the control-point/category pairs and the
        1,000 move lines. Use the scale option to increase only the move-line count.
    -->
    <record id="benchmark_move_line_quality_checks" model="populate.blueprint">
        <field name="name">Benchmark: Move Line Quality Checks</field>
        <field name="definition_xml" type="xml">
            <create model="product.category" count="20" id="quality_parent_categories" scale="False">
                <value name="counter" generator="misc.counter" start="1"/>
                <field name="name" eval="f'Quality Benchmark Category {counter:02}'"/>
            </create>

            <create model="product.category" count="100" id="quality_child_categories" scale="False">
                <value name="counter" generator="misc.counter" start="1"/>
                <field name="name" eval="f'Quality Benchmark Subcategory {counter:03}'"/>
                <field name="parent_id" ref="quality_parent_categories"/>
            </create>

            <create model="product.product" count="100" id="quality_products" scale="False" context="{'tracking_disable': True}">
                <value name="counter" generator="misc.counter" start="1"/>
                <field name="name" eval="f'Quality Benchmark Product {counter:03}'"/>
                <field name="type" eval="'consu'"/>
                <field name="is_storable" eval="True"/>
                <field name="tracking" eval="'none'"/>
                <field name="categ_id" ref="quality_child_categories"/>
            </create>

            <create model="quality.point" count="20" id="category_quality_points" scale="False">
                <value name="counter" generator="misc.counter" start="1"/>
                <field name="title" eval="f'Benchmark Category Control Point {counter:02}'"/>
                <field name="apply_to" eval="'categories'"/>
                <field name="product_category_ids" ref="quality_parent_categories" count="5"/>
                <field name="picking_type_ids" eval="[Command.set([env.ref('stock.picking_type_in').id])]"/>
                <field name="measure_on" eval="'move_line'"/>
                <field name="measure_frequency_type" eval="'all'"/>
                <field name="test_type_id" eval="env.ref('quality_control.test_type_passfail').id"/>
            </create>

            <create model="stock.picking" count="1" id="quality_picking" scale="False">
                <field name="picking_type_id" eval="env.ref('stock.picking_type_in').id"/>
                <field name="location_id" eval="env.ref('stock.stock_location_suppliers').id"/>
                <field name="location_dest_id" eval="env.ref('stock.stock_location_stock').id"/>
                <field name="origin" eval="'Quality control performance benchmark'"/>
            </create>

            <create model="stock.move" count="1000" id="quality_moves" scale="False" context="{'tracking_disable': True}">
                <field name="picking_id" ref="quality_picking"/>
                <field name="product_id" ref="quality_products"/>
                <field name="product_uom_qty" eval="1.0"/>
                <field name="uom_id" eval="env['product.product'].browse(product_id).uom_id.id"/>
                <field name="location_id" eval="env.ref('stock.stock_location_suppliers').id"/>
                <field name="location_dest_id" eval="env.ref('stock.stock_location_stock').id"/>
            </create>

            <create model="stock.move.line" count="1000" id="quality_move_lines" parallel="False">
                <field name="move_id" ref="quality_moves"/>
                <field name="product_id" eval="env['stock.move'].browse(move_id).product_id.id"/>
                <field name="uom_id" eval="env['stock.move'].browse(move_id).uom_id.id"/>
                <field name="quantity" eval="1.0"/>
                <field name="location_id" eval="env.ref('stock.stock_location_suppliers').id"/>
                <field name="location_dest_id" eval="env.ref('stock.stock_location_stock').id"/>
            </create>
        </field>
    </record>
</odoo>
```
The populate benchmark creates 20 quality points linked to 5 categories each, resulting in 100 point/category relationships. It then creates 1,000 move lines in one batch, generating +-4.5k quality checks.

Products belong to child categories while quality points target their parents, this represents large stock operations with category-wide quality rules.

|             | Before | After | Improvement |
|-------------|--------|-------|-------------|
| Time        | 11.8s  | 10.3s | 12.7%       |
| Query count | 12487  | 10120 | 19.0%       |

Reference
---------
task-6488454

## Before this commit:

- Variant images had to be uploaded and managed separately for each product
  variant.
- Even when multiple variants shared the same characteristics (e.g., the same
  image for all sizes of a blue T-shirt), the image had to be duplicated across
  variants.

## After this commit:

### 1. Image assignment using attribute values

- All images related to a product template, including variant specific images,
  are now visible in the Extra Media section on both the template and its
  variant forms.
- In the variant form, images that do not apply to the current variant (i.e.,
  belonging to other variants) are visually muted.
- Each image can be linked to specific attribute values using a dropdown in the
  kanban view.
- An image is applied to a variant only if the variant matches all attribute
  values assigned to the image.
- If none of the values of attribute is selected on the image, then that
  attribute will not affect the matching logic.
- In the product form view, images with attribute values are displayed first,
  followed by images without attribute values.

This removes unnecessary duplication and simplifies variant image management.

### 2. Shop page behavior

- The primary image is always the template's main image.
- The secondary image is the second template image.

### 3. Product page behavior

- For the selected variant:
  - Variant specific images are displayed first, with the first image serving as
    the variant's main image.
  - Template images without attribute values are displayed afterward.

### 4. Variant main image logic

- The first variant specific extra image is used as the variant's main image.
- If the user manually updates the variant's main image, the first variant
  specific extra image is updated to match it. If no variant specific extra
  image  exists, a new one is created using the main image.
- If no variant specific extra images exist, the variant falls back to the
  template's main image.

### 5. Template main image logic

- The first extra image is used as the template's main image.
- If the user manually updates the template's main image, the first extra image
  is updated to match it. If no extra image exists, a new one is created using
  the main image.

task-5405584

This commit adapts the overall UI of Discuss app to match with frost design.

1. Overall layout of Discuss app follows the floating box style of other Odoo screens

2. Messaging Menu style has been tweaked for improved readability: less muted items, better spacing, better visual of active item

3. Search bars are pilled-shaped to match search view.

4. Discuss app thread actions have style matching view switcher for panel actions.

5. Channel Member role iconography and action label has been changed to be more natural: crown icon, filled (owner) and unfilled (admin), "Set Member" for cleared downgrading of member role, consistent order of actions based on role hierarchy)

6. More visible border around core UI elements, like composer or message bubble.

7. Add People button has now an icon next to label.

8. Chat bubble message preview now is colored to match the message bubble color.

9. Notification Settings and Voice & Video Settings have their visual slightly simplified, with more spacing and less borders.

10. Call View actions and dropdowns no longer have weird gradient effect in simulated dark theme.

11. Call View Card's context menu stays open even when mouse leaving the card without any click away. Also improved color in this context menu.

12. Orange message bubble (mention to self) color has been tweaked to catch more the eye of the user.

13. Mentions style has been tweaked to pop a bit more.

14. Chat window outline is more separated from the background content through stronger border instead of shadow effect.

15. Add icons to Save as Template and Manage Templates in full composer.

16. Is typing text now shows member names in bold.

17. Autoresize, AutoresizeInput and DiscussContent's header have been fixed to properly follow the shrink-to-fit content aspect of header.

<img width="2137" height="563" alt="Screenshot 2026-09-04 at 12 35 50" src="https://github.com/user-attachments/assets/81d317f2-bb56-4bdf-81d8-5aaa07e4eb4b" />

### Contains the following commits:

https://github.com/odoo/o-spreadsheet/commit/bb7357a197 [REL] 19.5.0-alpha.16 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)
https://github.com/odoo/o-spreadsheet/commit/75ceb30aaa [FIX] Fonts: fix linux font on css variable [Task: 6452045](https://www.odoo.com/odoo/2328/tasks/6452045)
https://github.com/odoo/o-spreadsheet/commit/e8d059f38e [FIX] svg: remove unused commented SVGs [Task: 6317134](https://www.odoo.com/odoo/2328/tasks/6317134)
https://github.com/odoo/o-spreadsheet/commit/60c210afc2 [IMP] viewports_store: do not jump viewport on UNDO/REDO [Task: 6481352](https://www.odoo.com/odoo/2328/tasks/6481352)
https://github.com/odoo/o-spreadsheet/commit/537711e139 [FIX] chart: connect area charts through invalid values [Task: 6458796](https://www.odoo.com/odoo/2328/tasks/6458796)
https://github.com/odoo/o-spreadsheet/commit/ea25ccfa4b [FIX] css: update global gray colors to match Odoo [Task: 6515003](https://www.odoo.com/odoo/2328/tasks/6515003)

Co-authored-by: Florian Damhaut (flda) <flda@odoo.com>
Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com>
Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com>
Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com>
Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com>
Co-authored-by: Ronak Mukeshbhai Bharadiya (rmbh) <rmbh@odoo.com>
Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com>
Co-authored-by: Rémi Rahir (rar) <rar@odoo.com>
Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com>
Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
Co-authored-by: Marceline Thomas (matho) <matho@odoo.com>

In the Time Off step of a payrun, a half day time off was displayed half as wide as a full day one, making the gantt hard to read when scanning a month of time off.

Pill width comes from the grid: the leave gantt declares precision="day:half", so a day spans two grid columns and a morning or afternoon time off covers only one of them.

Override the precision to "day:full" on hr_leave_gantt_view_payroll, the primary view used by the payrun Time Off step and by the payroll time off action. A day is now a single column there, so half day and full day time off are displayed with the same width. The Time Off app gantt keeps its half day precision.

The multi selection counted the selected grid cells and divided them
by 2 to get a number of days. That only holds when a day is two cells,
so with the new precision selecting a single day displayed
"0.5 selected". Divide by the scale cellPart instead, which is the
number of cells in a day: 2 with day:half, giving the same result as
before, and 1 with day:full.

The `fetch_bus_notifications` method receives a dict mapping
channels to be fetched to their `last_fetched_id`, producing several
`channel_X = %s and id > %s` OR branches.

Since [1], notifications are fetched by DB, increasing the number of
OR branches.

Multiple ORs lead to O(n_row * n_groups) complexity as PostgreSQL has
to walk through each OR branch for each row.

A better approach is to JOIN the groups, which results in an O(n_row +
n_groups) complexity: PostgreSQL first builds the hash table then can
do a quick lookup for each row.

This is an order-of-magnitude win for large batches, with a negligible
difference for small ones.

[1]: https://github.com/odoo/odoo/pull/278597



------
Benchmark code, explain analyze for each case + plots:  [benchmark.zip](https://github.com/user-attachments/files/31776770/benchmark.zip)


Comparing old approach vs new approach with a growing amount of groups passed to `fetch_bus_notifications` on a 30k rows bus table. Median time over 50 run per batch.

<img width="400" alt="bench_no_index" src="https://github.com/user-attachments/assets/e8c8dbee-ed1a-4941-867c-9ac0f251693a" />

Purpose
=======
Improve the usability of the crm team switcher.

Specification
=============

1) Removing the "Pipeline" prefix from the switcher title.
Users will get that it's the specified team pipeline.

2) The "multi-memberships" settings shouldn't impact the switcher
visibility anymore. The team switcher is now visible as soon as
there's at least 2 teams using opportunities in the DB.
NB: The teams actually displayed in the switcher could be a subset of those
depending on the current user rights.

3) Adding an "All Sales Teams" option at the top of the team switcher acting as default.
The switcher will fallback to it when no team has previously been selected or
when the previously selected team cannot be found.
Selecting it will remove the team id filter from the domain and remove
the "default_team_id" context key from the context.
With this scenario, the default team on record creation will be set by
the crm.lead "team_id" field compute which will call "_get_default_team_id"
from the sales_team module.

Task-6485445

Description of the issue/feature this PR addresses:

When `im_livechat` (or any page) boots the OWL web stack with no `[data-hotkey]` / `withOverlay` targets, pressing Alt still called `preventDefault()` in `hotkey_service`. That blocked browser shortcuts such as Alt+D (focus address bar) on websites that embed the livechat scripts.

See https://github.com/odoo/odoo/issues/267928

Current behavior before PR:

- Pressing the overlay modifier (Alt, or Ctrl on macOS mapped to `"alt"`) always set `overlaysVisible = true` and called `preventDefault()`, even when there were no hotkeys to overlay.
- A follow-up key (e.g. D while Alt is held) then also hit `preventDefault()` because overlays were considered visible.
- Loading `/im_livechat/loader/...` + `assets_embed.js` on an external site therefore broke browser Alt shortcuts.

Desired behavior after PR is merged:

- `addHotkeyOverlays` returns whether overlays were actually displayed.
- `preventDefault` on the overlay modifier runs only when there is at least one overlay target.
- Pages with no hotkeys (typical livechat embed) leave browser shortcuts alone.
- When hotkeys exist, Alt still shows overlays and cancels the default, same as before.

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

Forward-Port-Of: odoo/odoo#284145

**Steps to reproduce:**
1. Create a product.
2. Add two attributes: multi-checkbox and any single-select type (e.g. Radio).
3. Publish the product and open its page on eCommerce.
4. Verify that no multi-checkbox option is selected by default.
5. Refresh the page twice.

**Issue:**
On the second page refresh, the first option of the multi-checkbox attribute is automatically selected, and the URL is updated with its parameter.

**Cause:**
- `_prepare_product_values` construct attribute combinations by mapping requested `attribute_values` query parameters line by line.
- When URL query parameters were present (e.g., set after the first refresh), the fallback logic `or ptal.product_template_value_ids.filtered('ptav_active')[:1]` treated unselected `multi_checkbox` attribute lines as missing required selections rather than empty selections, forcing them to default to their first active option.

**Fix:**
If no selection is provided for `multi_checkbox` line, return an empty recordset instead of falling back to the first active option.

opw-6494697

Forward-Port-Of: odoo/odoo#286492
Forward-Port-Of: odoo/odoo#284798

Since https://github.com/odoo/enterprise/pull/97488, the images are shared across spreadsheets and the attachments are no longer related to a specific record. Due to the management of the IrAttachment access rights, it means that those attachments are not accessible by anyone by default and we rely on the access_token to display them in the webclient.

However, the method that builds the final xlsx file fetches the images from the server and did not use the access token, meaning that it could never access the attachment. Such situation raised a UserError that was caught by the webclient.

How to reproduce:
- As admin, create a spreadsheet and insert an image inside of it
- try to download the spreadsheet as an xlsx file

counterpart of https://github.com/odoo/enterprise/pull/126384

Task-6432724

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

Forward-Port-Of: odoo/odoo#285981
Forward-Port-Of: odoo/odoo#279788

Steps to reproduce:
- Create a sale order with a down payment term.
- Invoice the down payment (down payment invoice A).
- Credit that down payment invoice directly (credit note A), without reconciling it with anything else.
- Generate the FatturaPA XML for credit note A.
- Observe that DatiFattureCollegate lists both down payment invoice A and credit note A itself, instead of only down payment invoice A. On an order with several down payment invoices/credit notes over time, every one of them is listed instead of just the document the current credit note actually reverses.

Cause of the issue:
_l10n_it_edi_export_data built downpayment_moves from self.invoice_line_ids._get_downpayment_lines().move_id with no filtering. _get_downpayment_lines() (sale override) returns every invoice line ever created against the same down payment sale order line, across the whole life of the order, not just the invoice the current document actually relates to. The template renders DatiFattureCollegate for every one of those moves unconditionally, on top of the already-correct reversed_entry_id/reconciled_moves fallback, including the current document itself.

Solution:
Restrict downpayment_moves to lines with a negative price_subtotal, mirroring the existing down payment deduction-line detection a few lines above, and explicitly exclude the current document. This limits DatiFattureCollegate's down payment entries to the case they are meant for: a final invoice actually deducting a previously invoiced down payment.

opw-6429716

Forward-Port-Of: odoo/odoo#285555
Forward-Port-Of: odoo/odoo#279938

Before this commit, the "Get A Booth" page of an event could keep listing the booths of the category checked on load after the visitor picks another one. Only a page reload brought the right ones back. The tour webooth_exhibitor_register timed out on that list:

FAILED: [5/13] Tour webooth_exhibitor_register -> Step Choose Booth (trigger: .o_wbooth_booths div:contains(OpenWood Demonstrator 2) input:not(:visible)).
TIMEOUT step failed to complete within 10000 ms.

This happens because the page fetches the booths of the category checked on load, and clicking another category fetches its booths while that first answer is still on its way. The answer coming back last fills the list, and the widget caches it under the category active on arrival, so the booths of the first category land in the cache of the clicked one.

This commit fixes the issue by caching an answer under the category it was asked for, and by filling the list only while that category is still the chosen one.

https://runbot.odoo.com/odoo/error/110527
https://runbot.odoo.com/odoo/error/161834

Forward-Port-Of: odoo/odoo#286552
Forward-Port-Of: odoo/odoo#286266

### Issue before this commit:
When generating a tax closing entry for France, the VAT credit carryover from the previous period is missing from the journal entry lines.

### Steps to reproduce the issue:
1. Download Accounting and l10n_fr
2. Go to Vendor > Bills
3. Create a vendor bill with date in June and price > 0 (ex. 1000$) and the 20% G tax that produce a 200$ VAT tax
4. Go to Customers > Invoices
5. Create an invoice with price > 0 (ex. 9000$), the date in July and the 20% G tax that will produce a 1800$ VAT tax
6. Go to Tax Return and validate all opened months up to July and see that for June the balance is -200$
9. Then go to View Entries of July using the 3 dots next to the "submit" button and see that there is no mentioning of the 200$ carry over of credit from the month before

### Cause of the issue:
The issue stems from a structural change in the core code where the logic to evaluate and balance the tax receivable account was removed from the _add_tax_group_closing_items method. Consequently, the VAT closing entry now only processes the current period's taxes and there is no reporting of any carried-forward VAT credits.

### Reason to introduce the fix:
French accounting rules strictly require the carried-forward VAT credit to be explicitly integrated into the current period's tax closing entry.

opw-6438648

Forward-Port-Of: odoo/enterprise#130377
Forward-Port-Of: odoo/enterprise#129181

Steps to reproduce:
- Create a July payslip for Bernice and mark it as paid
- Generate the meal voucher report for july
- Create 3 time off for Bernice in July
- Correct the payslip of July, in total we have 3 payslips now
- Create an August payslip for Bernice
- Create the meal voucher report for august

Pay attention to: everything has been created under "My Belgian Company" while Bernice is in the branch "My Belgian Office"

Current Behaviour:
When the august mealvoucher report is not marked as done, the postponed shows 0 for Bernice.

Expected Behavior:
When the report is not marked as done, august should have 3 mealvoucher postponed for Bernice.

The technical reasons behind this bug is that the SQL query for unreported payslips mapped to draft/ready reports filtered the payslips `company_id` on the mealvoucher `company_id`. But payslips for Bernice are under the branch "My Belgian Office" and the mealvoucher is created in "My belgian company".
The SQL query should take company branches into account, same as in `_get_corrected_payslips`.

task-6428719

### Issue
When creating a salary contract offer (smart button 'New Offer' in the employee form), a dimona action can be triggered, sending no-sense value to the government api.

### Reproducing steps
I've only been able to observe that by placing a breakpoint in the `hr.version.write` of the `hr_version.py` of `l10n_be_hr_payroll`:
- Create a master (1 sept. 2026) database with demo data and the following modules installed: `l10n_be_hr_contract_salary,test_l10n_be_hr_payroll_account`
- Set the dimona environment of the demo belgian company to 'Sandbox'
- Go to the employee Laurie Poiret
- Set the current contract end date to 1 day before today
- Create a dimona IN declaration for the last contract of Laurie Poiret (the one that has just been modified) (ctrl + k / DIMONA)
- On employee form: click on 'Check Dimona' and apply the response, the state of the dimona should appear ('Done')
- Create a new contract ('New Contract' button on the employee payroll tab) and set it to today
- Change the contract start date to tomorrow so that the dimona state become 'In progress'
- Click on the smart button 'New Offer'
- See that the `hr.version.action_update_dimona` is executed (but it shouldn't)

task-6521357

**Steps to reproduce:**
* Install **Accounting** module.
* Go to **Accounting → Bank → Transactions** (bank reconciliation widget).
* Open a transaction with a **positive** amount (e.g. a vendor sending money back).
* Click the three-dot menu on the transaction line and choose **Upload a Refund**.
* Upload any document (XML or PDF).

**Observed behavior:**
* A **Customer Credit Note** (`out_refund`) is created in a **sale** journal instead of a **Vendor Credit Note** (`in_refund`) in a **purchase** journal.
* The wrong document type means the reconciliation fails to link the refund against the correct payable account.

**Cause:**
* In `create_document_from_attachment` (`account_bank_statement.py`), the JS widget sends `type='sale'` in context when the transaction amount is positive (JS: `amount > 0 ? "sale" : "purchase"`).
* The original code mapped `type='sale'` → `default_move_type='out_refund'` (customer credit note) and searched for a `sale` journal — both wrong.
* Uploading from a bank statement is always a **vendor-side** operation: negative amount = vendor bill (`in_invoice`), positive amount = vendor refund (`in_refund`). The `type` context key from JS reflects transaction direction, not the accounting document type.
* Additionally, `in_refund` is a purchase document; Odoo's `_check_journal_move_type` constraint raises a `ValidationError` if a purchase document is created in a non-purchase journal, meaning the old code would crash at the ORM level for the refund path.

**Fix:**
* Map `type='sale'` → `default_move_type='in_refund'` (vendor credit note) instead of `out_refund`.
* Always search for a **purchase** journal regardless of the `type` context value, since both `in_invoice` and `in_refund` are purchase-side documents.

opw-6468779

Forward-Port-Of: odoo/enterprise#129385
Forward-Port-Of: odoo/enterprise#127912

**Steps to reproduce:**
* Install the **l10n_mx** localization.
* Enable **USD** and fetch the latest currency exchange rate from the settings.
* Configure **Quadrum** as the **PAC** in the settings.
* Create and sign a USD invoice with **16% IVA** (e.g. 4,500 USD + 720 USD tax = 5,220 USD total).
* Send the invoice to **CFDI**.
* Register a **partial MXN payment** that does not convert to a round USD amount (e.g. 30,000 MXN = 1,762.45 USD).
* Send the payment complement to the PAC by clicking **Update Payments** on the invoice.

**Observed behavior:**
The PAC rejects the CFDI with error **CRP20268**:
> El campo BaseP que corresponde a Traslado, no es igual a la suma de
> los importes de las bases registrados en los documentos relacionados
> donde el impuesto del documento relacionado sea igual al campo
> ImpuestoP de este elemento y la TasaOCuotaDR del documento
> relacionado sea igual al campo TasaOCuotaP de este elemento.

**Cause:**
* The SAT validator enforces a strict arithmetic relationship between three fields that are printed in the payment complement XML:
```
  BaseP == round(BaseDR / EquivalenciaDR, 6)
```
* When `percentage_paid` is a non-terminating decimal (which happens for any partial MXN payment against a USD invoice), the internal `raw_base` float carries more precision than the 6-decimal-place `BaseDR` that is actually written to the XML:
```
  percentage_paid = 1762.45 / 5220 = 0.33763409961685825...
  raw_base        = 4500 × 0.33763... = 1519.353448275862...
  BaseDR (XML)    = float_round(raw_base, 6) = 1519.353448
```
* The old code then used `raw_base` (the unrounded internal value) as the dividend when computing BaseP:
```
  BaseP (old) = float_round(1519.353448275862... / 0.0587483333, 6)
              = 25862.068980   ← written to <TrasladoP BaseP="...">
```
* The PAC performs the same division using only what it can read from the XML. The already-rounded BaseDR:
```
  BaseP (PAC) = round(1519.353448 / 0.0587483333, 6)
              = 25862.068975
```
* The 6th-decimal mismatch (25862.068980 ≠ 25862.068975) triggers CRP20268 and the document is rejected.

* The same issue occurs with a full MXN payment on a different date than the invoice when multiple invoice lines cause the rounded aggregate to diverge from the sum of per-line raw values.

**Fix:**
In `_l10n_mx_edi_add_payment_cfdi_values` (`account_move.py`), the block that builds the BaseP aggregation list was changed from iterating over raw per-`base_line` amounts to building a single synthetic entry per invoice using the already-rounded document-level `BaseDR` values (`tax_details['base']`) as the dividend:

  - Before : wrong: raw_base ≠ BaseDR printed in the XML
  'raw_base': tax_details['raw_base'] / inv_rate

  - After : correct: 'base' == BaseDR, the exact value in the XML
  'raw_base': tax_details['base'] / inv_rate

This guarantees that Odoo and the PAC divide the identical value, producing the identical 6-decimal result.

The `base_line_cfdi_values_mx_curr_list` path (used only for the `Totales` summary fields rounded to 2 dp) is left unchanged because the CRP20268 rule does not apply to that block.

opw-6468077

Forward-Port-Of: odoo/enterprise#128357

A consolidated invoice reports a range of PoS receipts per line, so every line claims that the receipts between its two endpoints follow each other. That claim was only loosely enforced: lines were built by walking every order of the sessions involved and breaking whenever one was not part of the batch. Two receipts that were both in the batch were therefore always merged, whatever sat between them.

This breaks down as soon as several devices sell under one config. Receipt numbers come from a counter local to each device, so two orders taken on two devices can carry adjacent numbers without being consecutive receipts, and were reported as a range covering receipts that were never part of it.

Lines are now built from an explicit continuity test on both `sequence_number`, gapless within a config, and the receipt reference read from `pos_reference`, which must name the same device and the next receipt number. Neither is sufficient alone: an order can reach the database later than its ticket was opened, so following sequence numbers do not imply consecutive receipts either.

A receipt made exclusively of refund lines is no longer merged into the line of the sales it follows. Refunds are usually rung up shortly after the sale they cancel, which made them contiguous with it and hid both inside a netted total - two sales and the two refunds cancelling them were reported as a single line of 0.00. An order mixing refund lines with new sales remains a receipt of its own, reported like any other with the amounts it refunded already deducted from it.

The orders linked to a consolidated invoice are also listed in the order in which they are reported on it, rather than in the reverse chronological one used by default for PoS orders, so that the two can be read together.

[task-6166533](https://www.odoo.com/odoo/my-tasks/6166533)

## Issue
When a use rmanually increases the invoiced quantity on a timesheet invoice, subsequent timesheets logged in future periods can no longer be invoiced. The system assumes that the most recent logged hours are already covered by the previously over-invoiced amount, blocking the billing of the most recent timesheet entries.

## Steps to reproduce
1. Install *Sales Timesheet* (`sale_timesheet`)
2. Create a Product P
    - Product Type: Service
    - Invoicing Policy: Based on Timesheets
    - Create on Order: (Project &) Task
3. Create an SO:
    - Customer: Any
    - Product: P (any quantity)
    - Confirm
4. Record hours on the task created:
    - 06/01/2026 (June 1st): 1 hour
    - 07/01/2026 (July 1st): 1 hour
5. Create the invoice for the June timesheet entry (by setting a timesheets period when creating the invoice), then **change the quantity to any value strictly greater than 2** and confirm.
6. Create the invoice for July
7. **An "Invalid Operation" error appears, stating that there's nothing to invoice, even though the timesheet entry from July was never invoiced.**

## Cause
Since https://github.com/odoo/odoo/commit/3b86ac3d180993239b63fd305ee0ba1f17f7eb20, the computation of the quantity to invoice changed to include the difference between the quantity delivered and the quantity already invoiced. In the flow described by the steps to reproduce above, the quantity to invoice is larger than the quantity delivered, making the `qty_to_invoice` equal to `0.0`.

https://github.com/odoo/odoo/blob/626d31fa0191bfe7ca8e1fcf177357eeeb60f2c7/addons/sale_timesheet/models/sale_order.py#L331-L334

The reason for the fix above being the partial refunding of timesheet-related invoices, we can keep that solution when working with refunded invoices, and keep the previous behavior for other cases.

This solution solves the issue in the steps to reproduce above, but was also manually tested on the issues from https://github.com/odoo/odoo/commit/3b86ac3d180993239b63fd305ee0ba1f17f7eb20 and https://github.com/odoo/odoo/commit/64cf4afabd0c5ef040cf87fc6f3125fe0bb81bbb.

opw-6485674

Forward-Port-Of: odoo/odoo#286301
Forward-Port-Of: odoo/odoo#284470

Steps to reproduce:
- Have an external VoIP software configured (e.g. Linphone)
- Have your Odoo configured and opened too
- Call your VoIP number, using your smartphone => Both the softphone and Linphone ring
- Answer or reject using Linphone => The VoIP call record in Odoo immediately switches from "Trying to call" to "Missed".

While there was no guarantee for our VoIP integration to work alongside Linphone in 19.0, we decided this should be an easy safe enough fix. Starting 19.2 (with [1]), the fix will be simplified and hopefully prettier thanks to the ameliorations that were made.

After this fix, provided Odoo is open while Linphone is used, the call records will now switch to the right terminated / rejected status, still immediately once Linphone answers / rejects.

In future versions and especially 20.0+, the system will be different and will allow way more features like this one to work better (e.g. here the call record only even exists if Odoo is opened while using Linphone and we won't have any information about the call duration).

[1]: https://github.com/odoo/enterprise/commit/942f32316ab02d8c739fe7fdd5ec2bdde472a68e

task-6449259

Forward-Port-Of: odoo/enterprise#130047
Forward-Port-Of: odoo/enterprise#127077

### Issue:
When an analytic plan has applicability lines with a company filter, the applicability is incorrectly applied on views that do not define a `business_domain`, such as Work Centers or Employee views

For example, if a plan has:
- Default Applicability: Unavailable
- A line with Domain: Invoice, Company: My Company, Applicability: Mandatory

Opening the analytic distribution on a Work Center shows `Mandatory` instead of the default `Unavailable`

### Cause:
In commit https://github.com/odoo/odoo/commit/ffcf2ee1a3185ef73db93bfd95625844506692c5 `_get_score` was updated to return `0.5` when the applicability line's company matches the caller's company, even when no `business_domain` is provided

In `_get_applicability`, the loop selects the first rule whose score exceeds the current minimum, which starts at `0`:
https://github.com/odoo/odoo/blob/710e056e5171af2ab72d7d7793da3518f12faf5e/addons/analytic/models/analytic_plan.py#L255-L264

A score of `0.5` is enough to win over the default applicability, so a company-only match on a domain-specific rule incorrectly overrides the default when no `business_domain` is passed

### Steps to reproduce:
- Install `mrp` and `accountant` with demo data
- Enable Analytic Accounting in Settings
- Open the Internal analytic plan and edit its applicability line:
  -- Remove the account prefix
  -- Default Applicability: Unavailable
  -- Domain: Invoice, Company: My Company (SF), Applicability: Mandatory
- Go to Manufacturing > Configuration > Work Centers
- Open any work center and click on Analytic Distribution

Before the fix, Internal is shown as Mandatory instead of Unavailable
Removing the company from the applicability line confirms the issue

opw-6404884

Forward-Port-Of: odoo/odoo#280312

Users who only have accounting rights (not the Settings > Users Companies > Access Rights group) get an access error on the Companies model when generating the BOE file for the Modelo 115 tax reports, even though exporting a BOE file has nothing to do with editing company configuration and should be available to any accountant.

Steps to reproduce:
-------------------
* Log in as a user with accounting rights only (not part of the Companies > Access Rights group)
* Go to Accounting > Reporting > Tax Return, open the Mod 115 report
* Click the gear icon > BOE > Generate BOE

> Observation:
An AccessError is raised: "You are not allowed to modify 'Companies' (res.company) ... This operation is allowed for the following groups:
Access Rights", even though the user is not trying to edit the company.

Why the fix:
------------
The BOE wizard shared by Mod 111/115/303 declares a `company_partner_id` field, related to `company_id.partner_id`, with `readonly=False`. That field is invisible in every view and only exists to compute the domain of `partner_bank_id`; it was never meant to be edited by the user. Because it is declared writable, the ORM attaches an inverse to the related field, so saving the wizard (which happens when generating the BOE, since the field, though invisible, is still part of the view and thus of the saved values) writes `company.partner_id` back onto `res.company`, even though the value never actually changes. That implicit write requires write access on res.company, which is only granted to the Access Rights group, causing the error for regular accountants. Dropping `readonly=False` keeps the field as a plain readonly related field, still usable for the bank account domain, without ever triggering that spurious write.

opw-6388869

Forward-Port-Of: odoo/enterprise#130168
Forward-Port-Of: odoo/enterprise#126661

When the quantity of a make-to-order manufacturing order is changed, its finished move is copied to propagate the extra quantity downstream. In some cases (after splitting then merging back productions) that copy is not merged back, so the order ends up with two finished moves for the same product.

On validation, two things then go wrong:
- _post_inventory writes the produced quantity on each finished move,
  so both get the full quantity and the production is doubled
- mrp_account._cal_price prices the finished move and calls
  ensure_one(), which raises "Expected singleton" for an average/fifo
  product, so "Produce All" fails

Split the produced quantity across the finished moves with unit_factor (like _set_qty_producing already does), and price them as a whole instead of expecting a single finished move.

Steps to reproduce:
- Create a BoM for product A with the MTO route, and a component B
- Create a Sale Order for 30 units of A, confirm it
- Split the MO into 3 productions of 10, merge two of them
- On the third, Update Quantity 10 -> 15, then Produce All
- The product should be produced once (15, not 30), with A valued in
  average/fifo it instead of an error.

opw-6242504
opw-6310972
opw-6307025
opw-6354739

Forward-Port-Of: odoo/odoo#286173
Forward-Port-Of: odoo/odoo#269254

Issue:
When a user selects a generic appraisal template other than the first one, confirming or resetting the appraisal silently replaces that selection with the first generic template. Filtering appraisals by the originally selected template then fails to return the appraisal.

Steps to reproduce:
* Configure multiple appraisal templates without department restrictions.
* Create an appraisal and select a template other than the first one.
* Confirm the appraisal.
* Filter appraisals by the selected template.

Cause:
`_compute_appraisal_template()` only preserved templates directly linked to the appraisal's department. Generic templates have no department relation, so a valid selected template was discarded whenever the computation was triggered by a state dependent department recomputation. The generic fallback then stored the first template instead.

https://github.com/odoo/enterprise/blob/5c57ccbb13269af28de0a6c7f35454be52424f43/hr_appraisal/models/hr_appraisal.py#L195-L209

Solution:
We need to distinguish the generic default loaded on an unsaved form from a compatible generic template already stored on an appraisal. Preserve the latter across recomputations while retaining department template priority during creation and rejecting templates that no longer match the appraisal's department or company.

opw-6449041

Forward-Port-Of: odoo/enterprise#129635
Forward-Port-Of: odoo/enterprise#127566

### Steps to Reproduce:
1. In Debug mode, go to Aliases
2. Click on any active Alias, ex. customer-care
3. Click on "Open Parent Document" smart button
4. Click on "Tickets" smart button and observe error

### Description of the issue/feature this PR addresses:
**Issue:** When navigating from an email alias to its parent document (e.g., a Helpdesk Team), the web client incorrectly retains the  `active_id` and `active_model` of the alias in the context.

**Solution:** We updated the `action_view_ticket` method in `helpdesk.team` to explicitly inject the correct `active_model` and `active_id` into  the context before calling `_for_xml_id`. This overwrites the polluted Alias data before the window action is evaluated.

### Current behavior before PR:
Clicking the "Tickets" smart button passes the old alias context into the action. This bad data flows into the ticket view, which attempts to look up a Helpdesk Team using the Alias's ID to generate the empty list help message, resulting in a `MissingError`.

### Desired behavior after PR: 
The Python action sanitizes the context at the source, ensuring that the XML action and subsequent view evaluations receive the correct Helpdesk Team ID. Ultimately, the view will load normally without crashing.

opw-6395638

Forward-Port-Of: odoo/enterprise#130088
Forward-Port-Of: odoo/enterprise#125232

**Steps to reproduce:**
- Install the `website_sale` module.
- Configure the Mollie payment provider and publish it.
- Enable the PLN currency.
- Create a PLN pricelist and make it selectable on the website.
- Open the Mitchell Admin customer record and, under the `Sales & Purchase` tab, assign the USD pricelist.
- Go to the website shop, switch the pricelist to PLN, add a product to the cart, and proceed to checkout.
- Pay through Mollie and mark the transaction as paid in Mollie.

**Issue:**
- After a successful redirect payment, the confirmation page displays an amount-mismatch warning, even though the payment was accepted by the provider for the correct amount.

**Root cause:**
- Mollie's return request and webhook can arrive within milliseconds of each other. Both requests attempt to create a `payment_data` record referencing the same `payment_transaction`.
- At the same time, the cron holds a `FOR UPDATE` lock on the transaction while processing the first payload. The `FOR KEY SHARE` lock automatically acquired by PostgreSQL during the foreign-key check of the `payment_data` insertion conflicts with this `FOR UPDATE` lock. This results in a serialization failure and rolls back the post-processing job that would have confirmed the sale order (`draft` → `sale`).
- This temporarily leaves the transaction in `done` state while the sale order is still in `draft`.
- `sale_reset()` then clears both the session cart key and the selected- pricelist key. When `/shop/confirmation` renders, `request.cart` is resolved through `_get_and_cache_current_cart()`. The abandoned-cart recovery branch finds the still-draft sale order and calls `_update_address()` on it.
- Since the selected-pricelist key is no longer present in the session, the customer's default USD pricelist is applied. `_recompute_prices()` then changes the sale order total. However, the payment transaction still contains the original PLN amount, so `_get_status_message()` detects the difference and displays the amount-mismatch warning.

**Solution:**
- Before calling `_update_address()` and `_verify_cart()` on an abandoned-cart candidate, check the state of its latest transaction.
- If the transaction is `pending`, `authorized`, or `done`, discard the candidate and return an empty cart.
- This matches the guard already present in the session-cart branch of the same method, keeping both paths consistent.
- The serialization failure itself is expected and handled by Odoo's retry mechanism. This fix prevents the resulting side-effect window from allowing an already-paid order to be recovered as an abandoned cart and repriced.

opw-6470325

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

### [REF] website, *: prevent style in navbar of translated table of content

*: html_builder

The snippet "Table of Content" copies the content of the title in its navbar, taking care of removing style to have plain text in the navbar. In translate, to try to achieve this as well, it uses some special logic with `o_translation_without_style`, a second translation hash,... But, if one of the title has no style in the original language, but a translation adds a style, then the term with style is used in the navbar.

This commit uses `o_translate_inline` on the links of the navbar. With this, they make together a single translation term which is always distinct from the terms of the titles. The copy of the translated titles is made with the same plugin as in normal mode (with some adaptation to take into account the translation spans).

Steps to reproduce:
- Open website builder
- Drop the "Table of Content" snippet
- Save
- Open website builder in translate mode
- Select text in a title of the "Table of Content" snippet
- Change its style: make it bold
- Save
- Bug: the term in the navbar is bold as well

task-6304267

### [REF] website: define style for translated social snippet in main css

The snippets "Social Media" and "Share" needs additional rules to appear correctly in translate mode (if they have `o_translate_inline` on their links). Those were defined in a separate file for inside the builder. This is error prone because the content of those rules needs to be kept in sync with the general rules.

To avoid the duplication, this commit moves those additional rules with the normal ones, so they share their content.

task-6304267

In this PR, https://github.com/odoo/odoo/pull/186250, the `product_uom` field was renamed to `product_uom_id`. However, in the `delivery` module, `product_uom_id` is dropped from the values when the delivery line is created. 
This causes `product_uom_id` to be recomputed.

This commit reintroduces `product_uom_id` in the values to prevent the field from being recomputed.

**Description of the issue/feature this PR addresses:**

For a strange reason, when a module inherits from `sale.order.line` and adds some computed fields with `precompute=True`. `price_unit`, `price_subtotal`, and `price_total` are computed incorrectly.

I have attached a module to demonstrate the issue.

https://github.com/user-attachments/assets/ebdd8695-c9d8-477b-b5cf-ba6d8d41e84a

Without this change, the test fails, and Odoo incorrectly recomputes the fields, as shown in the video.
<img width="1232" height="515" alt="image" src="https://github.com/user-attachments/assets/27370f1f-e7b7-4102-a606-0181b9d1a97a" />

When the ORM computes fields marked as `precompute=True`, in this function `_add_precomputed_values` https://github.com/odoo/odoo/blob/0d44f26d9b0fb1c1a5db463cf1f8dd0d3c72ba26/odoo/orm/models.py#L4836, `price_unit` is 0, but the records get `price_unit` from the product. Therefore, when [_compute_amount](https://github.com/odoo/odoo/blob/0d44f26d9b0fb1c1a5db463cf1f8dd0d3c72ba26/addons/sale/models/sale_order_line.py#L855) is called, the values are computed with an incorrect `price_unit`.
<img width="1087" height="940" alt="image" src="https://github.com/user-attachments/assets/92feadf0-7f93-4acc-8f1a-931db0655fcc" />

**Steps to reproduce the issue:**

- Install the attached module. [sale_precompute.zip](https://github.com/user-attachments/files/31265993/sale_precompute.zip)
- Configure a delivery carrier as free for orders over 1, and set the fixed price to 5, for example.
- Create a sales order and add a product with a value greater than 1.
- Add the shipping method. The price should be 0. In the sales order line, `price_unit` is 0, but `price_subtotal` and `price_total` are equal to 5 (the product's sale price).

For more context, this module is a simple example extracted from the OCA `product_secondary_unit` module, which adds a mixin with these fields: https://github.com/OCA/product-attribute/blob/18.0/product_secondary_unit/models/product_secondary_unit_mixin.py. In the `sale_order_secondary_unit` module, `sale.order.line` inherits from this mixin.

You can see the error in this PR: https://github.com/OCA/sale-workflow/pull/4535.
https://github.com/OCA/sale-workflow/actions/runs/32259842816/job/96090194021?pr=4535#step:8:509

I understand that this requires a deeper investigation into precompute to solve the underlying issue, but I propose setting `product_uom_id` in the `_prepare_delivery_line_vals` method as a temporary solution while the final solution is being investigated.

I understand that this field should not have been removed from `_prepare_delivery_line_vals`; the referenced PR only renamed the field and did not intend to remove the value from this method.
@Tecnativa @pedrobaeza @kcv-odoo @Feyensv coudl you please review this?

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

Forward-Port-Of: odoo/odoo#284316
Forward-Port-Of: odoo/odoo#283551