Original PR description

*: account_reports, appointment, knowledge, l10n_us_reports, planning, sign, social, social_crm, spreadsheet_edition, web_studio

- requires : https://github.com/odoo/odoo/pull/204473
-----------------------

This PR replaces all the existing occurrences of `fa-ellipsis-*` with the new `oi-ellipsis-*` icons.

Prior to this PR, we were relying on Font Awesome ellipsis icons which comes with squared dots that look quite bulky.
As the ellipsis icon is shown in some key places, we decided to slightly tweak it to improve the visual result.

Note that the fa-ellipsis-* still exist and remain available but in order to maintain the consistency, we highly recommend to use `oi-ellipsis-v` and `oi-ellipsis-h` from now on.

task-4551038

Original PR description

We adapt a studio test to the changes brought by https://github.com/odoo/odoo/pull/205180

Original PR description

part of task-4712367.

community: https://github.com/odoo/odoo/pull/205186

Original PR description

If an order is send to the preparation display from a retail shop `false` was shown as card name. This was because `floating_order_name` is not used in retail shops.

New behavior from retail shop:
- Order card name is `tracking_number (pos_reference)`

New behavior from restaurant:
- Order card name is `floating_order_name` or `Direct Sale` or `table_number`.

taskId: 4711882

Forward-Port-Of: odoo/enterprise#83028

Original PR description

Added condition on a check in microsoft calendar that ensured the organizer was an attendee on the event on create. This was added in a change that allowed the organizer to be changed on the Odoo side. However, this caused issues with the appointments app when creating an appointment that only used resources. The "organizer" who in this case is the creator of the appointment type would not be an attendee and therefore would cause an error and make the appointment type unbookable.

Adding this condition allows the appointment to bypass the check if the appointment type uses resources instead of users.

This change adds the necessary override in enterprise. See change in community here: https://github.com/odoo/odoo/pull/178142

opw-3841495

Forward-Port-Of: odoo/enterprise#82866
Forward-Port-Of: odoo/enterprise#69036

Original PR description

Issue
=====
When displaying the Barcode move line form view on mobile, a traceback can happen.

How to reproduce
================
- Open the Barcode app on a mobile device (or use devtools to simulate a mobile device;)
- Create a new receipt;
- Click on "Add Product" and select a product with an existing quant;
- Confirm then re-open the move line's form view -> Traceback.

Cause of the issue
==================
In mobile view, the product's quants displayed in the move line form view are displayed as kanban record. This kanban view template use the `many2one_uom` widget but doesn't include the `product_id` field which make this widget not usable. By the way, those records are not editable so it makes no sense to use this widget in this case. To fix the issue, remove the widget where it is not needed/not usable.

Community PR: odoo/odoo#204252

Forward-Port-Of: odoo/enterprise#82684
Forward-Port-Of: odoo/enterprise#82640

Original PR description

Description of the issue this commit addresses:

In january 2025, updates were made to some sections of the LU tax report and chart of accounts. Therefore, the version we use is out of date.

---

Desired behavior after this commit is merged:

The COA and VAT reports use the new values updated in 2025.

---

Community PR: https://github.com/odoo/odoo/pull/202228
task-4587067

Forward-Port-Of: odoo/enterprise#82912
Forward-Port-Of: odoo/enterprise#81644

Original PR description

## Pull Request HOOT (PRHOOT) 30

This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details.

Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk.

Community: https://github.com/odoo/odoo/pull/203713

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

Forward-Port-Of: odoo/enterprise#83065
Forward-Port-Of: odoo/enterprise#82351

Original PR description

Following commit 6b5acdde9998fb1ee0d4d4aee0ab2375e50d7703 we ensured that we stopped the stock synchronization when there was a discrepancy between an offer fulfilment channel and an order fulfilment channel.

This bugfix didn't consider the cases of offers that were synced once then never updated with the changes of the new API, thus not being the string of a dictionary, but instead, being the string of an int. Thus raising an attribute error, and not a JSON error nor a TypeError.

These offers, though, don't need that safety net, and can thus just be ignored. If their stock needs to be sync someday, the stock cron will take care of these.

opw-4684657
opw-4684605

Forward-Port-Of: odoo/enterprise#83023

Original PR description

Before this commit:

Multi-package delivery validation for the carrier 'loomis' results in an error.
Rate is calcuated in the first request for all the packages.
Response of the second request is code 201 but with a warning message of rate already calcuated for the whole shippment.
Which reults in invalid operation error.

After this commit:

Added a check for 'LoomisExpress' to avoid the rate error from blocking validation.
Multi-package delivery is validated correctly.

opw-4650347

Forward-Port-Of: odoo/enterprise#82682

Original PR description

Some keys were not correclty translated

Steps to reproduce:
-------------------
* Install l10n_pe_reports_stock
* Switch to PE Company and Spanish language
* In Stock create a new operation
* Open the dropdown Type of Operation (PE)

> Observation: 

Why the fix:
------------
Based on official values
https://www.sunat.gob.pe/legislacion/superin/2015/anexo3-rs169-2015.pdf
Tabla 12


opw-4653572

Forward-Port-Of: odoo/enterprise#82692

Original PR description

Purpose
=======

Since: https://github.com/odoo/enterprise/commit/65b4e343ce9b16ef77f6c967314c48d0b10972bc The amounts are aggregated outside of the rule enumeration in the case there are several inputs for which the code is matching the salary rule code.

But in the case the rule code is not the same as the other input code, only the last amount is retrieved, not the total amount.

TaskID: 4711431

Forward-Port-Of: odoo/enterprise#83043

Original PR description

This PR excludes the employees that started after the 30/06 of the
13th month. They are not elligeable as they started more than 6 months
before the payment of the bonus.

As part of this PR, the computation of the correct tax rate has been
fixed. The amount is bounded so that a tax rate can always be computed.

task-4583139

Forward-Port-Of: odoo/enterprise#79923

Original PR description

Steps:
- Navigate to Management > Time Off > Gantt View.
- Click on a pill to open the popover.

Issues:
- The date format in the title showed 30/10/2025 instead of 03/10/2025.
- Causing inconsistency between the title and the Gantt view.

Fix:
Updated date formatting to ensure the title and popover both display dates are same in the MM/DD/YYYY format with leading zeros.

Task - 4660785

Forward-Port-Of: odoo/enterprise#81890

Original PR description

Forward-Port-Of: odoo/enterprise#83047

Original PR description

account_intrastat_report.xml: missing SUCode for xml report generation in l10n_de_intrastat

build_error-160011

Forward-Port-Of: odoo/enterprise#81066

Original PR description

See community PR odoo/odoo#204757 for the bugfix.

This commit adds a step to the scale tour to check that the computed price in the popup matches the expected value. The tour is also refactored slightly to make use of POS test helpers.

task-4702650

Forward-Port-Of: odoo/enterprise#82873

Original PR description

This doesn't end up blocking any flow, but it's confusing to have the warning there. l10n_br_edi_avatax_data is deliberately cleared after EDI, because it's no longer needed afterwards.

opw-4673601

Forward-Port-Of: odoo/enterprise#82925

Original PR description

Discounts on non recurring products were being recomputed every time the subscription was paused and resumed. Added a protecting similar to action_confirm in order to prevent this behavior.

opw-4440500

Forward-Port-Of: odoo/enterprise#82858

Original PR description

This commit fixes an issue with the public sidebar. When you unfold an article
the unfolding method was never linked to all the elements needed to unfold any
children article.

Now when clicking on the unfold button, we are adding the event on each children
of the unfolded articles.

Forward-Port-Of: odoo/enterprise#82349
Forward-Port-Of: odoo/enterprise#82003

Original PR description

In this commit:
-------------------
- If we have custom description applied in the sale order for any product that custom description
  would be reflected as it is on the invoice when we settle that SO from POS.

Task - 4645762

Original PR description

task-4715664

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

Original PR description

New PR: https://github.com/odoo/odoo/pull/205405

Original PR description

**Current behavior before PR:**

When a thread is created from a message, the message author
is not automatically added as a member of the thread.

**Desired behavior after PR is merged:**

The message author is implicitly added as a member when a
thread is created from message.

**Task**-4656632


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

Original PR description

Description of the issue/feature this PR addresses:

> - When we open the POS register, products get cropped and zoomed in version 18.0

Link to OPW :[4571051](https://www.odoo.com/odoo/project/70/tasks/4571051)

**Steps:**

> - Install module: point_of_sale
> - Open Point of sale -> Continue selling in dashboard -> and show the images

Current behavior before PR:

    Before fix:
![POS_BEFORE](https://github.com/user-attachments/assets/c4ca301a-e364-4963-9bba-48c506b5f714)

    After fix:
![POS AFTER](https://github.com/user-attachments/assets/1428a9be-ba8f-47ea-b0f5-110c0f09b7ec)


Desired behavior after PR is merged:

     - All product images are appropriately shown after my fix
     - The issue comes in version 18.0, saas~18.1 and saas~18.2


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

Original PR description

Issue:

Server error raised when selecting a project in a new task field added to a contact form

Steps to reproduce:

- Go to Contacts > select a contact
- Click on toggle studio
- Add the 'task' field in the contact form
- Go back to the contact
- In the task field, add a line
- Select a project

an error is raised

This fix is to properly handles NewId objects in the domain construction.

opw-4575975

Original PR description

Before this commit, in the `mountWithCleanup` test helper, the same `env` object was passed to both the given component and the main component container.

This is wrong as in some cases, the env given to the given component should include sub-env specific information, like the `config` key given to the `View` component (that shouldn't be given to the container).

This commit ensures that these `env` objects can be configured separately.

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

Original PR description

In this commit, we prefer to use click on element instead of press Tab
because tab will directly focus the other range period input.

Original PR description

New PR: https://github.com/odoo/enterprise/pull/83169

Original PR description

In this commit, we're refactoring macro.js by completely changing
its operation.
To detect triggers in the DOM, we no longer rely on DOM mutations, but
instead check for each frame to see if the trigger is in the DOM.
Once the trigger is found, we perform the action and move on to the
next step.
This significantly simplifies understanding of how macro.js works,
tours, and, more importantly, the bugs that can occur in tours.
This also avoids many indeterministic errors that could occur in the
tours due to the completely arbitrary "checkDelay" parameter (the time
period after which there are no more mutations before the element is
checked to see if it is in the DOM).
This checkDelay parameter is therefore no longer used.
It will be completely removed from the codebase in a future PR.

Original PR description

- have a follower with a portal partner linked to a specific company
  "portal" user is important here because internal users don't have multi-company rule.
- view the chatter with a user which has no access to that company
- the chatter is currently locked by an ACL error

The follower should be displayed instead.

task-4648765

Forward-Port-Of: odoo/odoo#203808
Forward-Port-Of: odoo/odoo#201864

Original PR description

Steps to reproduce
==================

- In 18, go to a view with an always invisible many2one field
- Enable debug mode
- In the debug menu, click on "Set defaults"

=> Cannot read properties of undefined (reading 'length')

Cause of the issue
==================

We only fetch the display name for many2one that are not always invisible

https://github.com/odoo/odoo/blob/6a1c38a83a1a9108ae4cbfe36bf787bef02de063/addons/web/static/src/model/relational_model/utils.js#L383-L384

In that case, `displayed` will be undefined.

a0732ec87edbb7fee6ebc76ea093bc8a52fd3fad didn't check if displayed was defined. It also checked the length of non-string values. While it doesn't cause an error, it doesn't make sense.

A comparison of `typeof displayed === "string"` is not enough, because we also need to handle Markup elements.

opw-4572496

Forward-Port-Of: odoo/odoo#205256
Forward-Port-Of: odoo/odoo#204816

Original PR description

Because #203874 needed to manipulate Odoo imports, it had to be able to import Odoo. Turns out there are setups where the root of the community repository is on `sys.path` but not in `PYTHONPATH` which can lead the pylint invocation to be confused and not have `odoo` be reachable from the `PYTHONPATH`, thus crashing the plugins' loading.

Thus to run pylint we need not the `PYTHONPATH` but the `sys.path`. Which is not ideal because that'll contain the paths to the site and standard library of the python running the test, which might be different than the python running pylint.

To limit the risks of contamination, strip out any path starting with one of the `sys.$CATEGORY_prefix` entries.

Forward-Port-Of: odoo/odoo#205194

Original PR description

### Description:

When confirming a sale order with products on MTO, it can trigger the method _run_manufacture to generate the manufacturing order linked to it. However, this part can take a long time to be processed because of the multiple compute stored triggered on the way (mostly from the field `move_finished_ids`).

### Fix:

To speed this up, we can extract the deletion of the previous finished moves so the ORM can batch delete in `_compute_move_finished_ids`.

### Benchmark:

| # of lines with MTO | Before  | After  |
|---------------------|---------|--------|
|  20                 |    3:48 |   2:48 |
|  10                 |    1:45 |   1:18 |

### Reference:

opw-4629884

Forward-Port-Of: odoo/odoo#204808

Original PR description

* applies to: `l10n_in_edi_ewaybill`, `l10n_in_ewaybill_stock`

* Before this commit: When there were multiple alerts, the code handled all alert messages correctly and calculated the `distance` as expected. However, when there was only a single alert related to distance, the process would get stuck.

* After this commit: The code now also handles cases with a single distance-related alert message, ensuring proper detection and processing in all scenarios.

> No Task ID


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

Forward-Port-Of: odoo/odoo#205054

Original PR description

Steps to reproduce:
- Install apps accounting, purchase and stock.
- Create a PO with a different currency than the main currency.
- Add a least one PO line.
- Confirm the PO and mark the quantities as received.
- Create a vendor bill and try to link the PO -> Traceback.

Since commit 90158f6, the `balance` of the `account.move.line` is computed before the call to `_compute_all_tax` when importing a PO. Before, it wasn't computed yet and was equal to 0. The line `amount_currency` isn't computed yet at this point, it is always 0.

Since the `rate` is computed as `amount_currency`/`balance`, it is always computed to 0, which then causes a `ZeroDivisionError` in further computations.

[opw-4710499](https://www.odoo.com/odoo/project/967/tasks/4710499)

Forward-Port-Of: odoo/odoo#205195

Original PR description

The UNECE code mapping for Nilvera was done in l10n_tr_nilvera_einvoice.
here at #193030 
However later that was needed in l10n_tr_nilvera_edespatch and 
that too in stock_move.
This PR moves the mapping from l10n_tr_nilvera_einvoice to l10n_tr_nilvera
so that it can be used by both einvoice and edespatch.

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

Forward-Port-Of: odoo/odoo#204457

Original PR description

Following commit 6b5acdde9998fb1ee0d4d4aee0ab2375e50d7703 we ensured that we stopped the stock synchronization when there was a discrepancy between an offer fulfilment channel and an order fulfilment channel.

This bugfix didn't consider the cases of offers that were synced once then never updated with the changes of the new API, thus not being the string of a dictionary, but instead, being the string of an int. Thus raising an attribute error, and not a JSON error nor a TypeError.

These offers, though, don't need that safety net, and can thus just be ignored. If their stock needs to be sync someday, the stock cron will take care of these.

opw-4684657
opw-4684605

Forward-Port-Of: odoo/enterprise#83023

Original PR description

Before this commit:

Multi-package delivery validation for the carrier 'loomis' results in an error.
Rate is calcuated in the first request for all the packages.
Response of the second request is code 201 but with a warning message of rate already calcuated for the whole shippment.
Which reults in invalid operation error.

After this commit:

Added a check for 'LoomisExpress' to avoid the rate error from blocking validation.
Multi-package delivery is validated correctly.

opw-4650347

Forward-Port-Of: odoo/enterprise#82682

Original PR description

Purpose
=======

Since: https://github.com/odoo/enterprise/commit/65b4e343ce9b16ef77f6c967314c48d0b10972bc The amounts are aggregated outside of the rule enumeration in the case there are several inputs for which the code is matching the salary rule code.

But in the case the rule code is not the same as the other input code, only the last amount is retrieved, not the total amount.

TaskID: 4711431

Forward-Port-Of: odoo/enterprise#83043

Original PR description

Vendor bills and purchase orders should always be negative on a budget with type `both`, as they are expenses. 

- Create a budget with type `both`
- Create a sales invoice and several purchase orders and vendor bills
- The budget report's purchase order amounts are positive and added up.
  As soon as they are billed they become negative.

Task [link](https://www.odoo.com/odoo/project/967/tasks/4568067)
opw-4568067

Forward-Port-Of: odoo/enterprise#81356

Original PR description

Some keys were not correclty translated

Steps to reproduce:
-------------------
* Install l10n_pe_reports_stock
* Switch to PE Company and Spanish language
* In Stock create a new operation
* Open the dropdown Type of Operation (PE)

> Observation: 

Why the fix:
------------
Based on official values
https://www.sunat.gob.pe/legislacion/superin/2015/anexo3-rs169-2015.pdf
Tabla 12


opw-4653572

Forward-Port-Of: odoo/enterprise#82692