Original PR description

Batch action provides only the pin as a string. We had a traceback when trying to get `high_level_message` as if the data provided was a dict.

Original PR description

When accessing the API documentation endpoint (`/doc`), the server could crash with an Internal Server Error if the database contained ir.model records for models that are not loaded in the current registry.

Steps to reproduce:
1. Insert a record into `ir_model` with `model='ghost.model'` and `state='base'`.
2. Open `/doc`.
3. The server raises a `KeyError: 'ghost.model'`.

Root Cause:

The `/doc` endpoint iterates over all records in `ir.model`. For each record, it attempts to resolve the Python class using `self.env[ir_model.model]` to check access rights. If a model exists in the database with `state='base'`, Odoo expects it to be defined in the Python source code and does not generate it dynamically. If the corresponding Python class is missing (e.g., from an old module), it is never added to the registry, causing the lookup to fail with a `KeyError`.

opw-5401782

Forward-Port-Of: odoo/odoo#241483

Original PR description

* Fix _compute_l10n_ch_legal_name method to correctly assign first_name and last_name from employee name (was previously reversed)

* Update all SwissDEC test data to use correct "FirstName LastName" format instead of "LastName FirstName" to match the corrected computation logic

task-5102851

Forward-Port-Of: odoo/enterprise#104067
Forward-Port-Of: odoo/enterprise#95252

Original PR description

### Steps to reproduce:

- In the settings enable "Rental Transfers"
- Create a storable and rentable product P
- Create and confirm a rental order for 1 unit of P
- Change the rental period to 10 days in the future
#### > The rental tranfers were not updated accordingly

### Cause of the issue:

Nothing is currently implemented to reschedule the rental transfers.

### Fix:

We somewhat mimic the reschedule purchase behavior: https://github.com/odoo/odoo/blob/6ca34a0f5347e0611cde95453119dda8b40fa589/addons/purchase_stock/models/purchase_order_line.py#L98-L101
But we rely on the order itself rather than its order lines since the `start_date` and the `return_date` are related fields so that no `write` is triggered when the order is rescheduled:
https://github.com/odoo/enterprise/blob/96a80f583a0ca502ff06bc05d03775c76c6a7537/sale_renting/models/sale_order_line.py#L18-L19

opw-5158508

Forward-Port-Of: odoo/enterprise#103602
Forward-Port-Of: odoo/enterprise#101334

Original PR description

**Description of the issue/feature this PR addresses**: Integer rounding is only required on annual l10n_it VAT reports. It appears that it was incorrectly added to the monthly report when the two were split in #193662.

**Current behavior before PR**: Integer rounding on monthly l10n_it tax reports.

**Desired behavior after PR is merged**: No more integer rounding on monthly l10n_it tax reports.

[opw-5292310](https://www.odoo.com/odoo/project.task/project.task/5292310)

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

Forward-Port-Of: odoo/odoo#244389
Forward-Port-Of: odoo/odoo#243100

Original PR description

Integer rounding is only required on annual l10n_it VAT reports. It appears that it was incorrectly added to the monthly report when the two were split in [#193662](https://github.com/odoo/odoo/pull/193662).

[opw-5292310](https://www.odoo.com/odoo/project.task/project.task/5292310)

Forward-Port-Of: odoo/enterprise#104679
Forward-Port-Of: odoo/enterprise#103852

Original PR description

**Steps to reproduce**
- Install `hr_work_entry_attendance`
- Delete one of the overtime rules from the "Default Ruleset", e.g. "Employee Schedule Rule"
- Upgrade the `hr` module
- Traceback: `psycopg2.errors.CheckViolation: new row for relation "hr_attendance_overtime_rule" violates check constraint "hr_attendance_overtime_rule_if_paid_work_entry_type_defined"`

**Cause**
The `_if_paid_work_entry_type_defined` constraint added by the `hr_work_entry_attendance` module on overtime rule records will fail when re-creating an overtime rule record when upgrading another module than `hr_work_entry_attendance`, since the module is not loaded and we don't get a default value for the `work_entry_type_id` field.

**Fix**
Since the ORM cannot manage that, disable forcecreate for these records.
Related: https://github.com/odoo/enterprise/commit/f935e62bae7f204ea3f6db8f08b173bdf011c0d2

opw-5428542

Forward-Port-Of: odoo/odoo#244333

Original PR description

…s args

See https://github.com/odoo/o-spreadsheet/commit/6533266efa

Task: 5095364

Original PR description

Before this commit, a test in iot was looking at the 'values' key of a LazyTranslatedString to make an assertion.

This is not robust, as this is an implementation detail internal to the translation system.

To fix this, the translations have been "allowed" (i.e. loaded) in the test, ensuring that the returned value is a string and not a lazy-translated string.

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

Original PR description

The standard price of the products were not converted to the currency of the PoS journal, which could lead to issues when creating pricelist items based on the standard price.

Steps to reproduce:
-------------------
* Change the currency of any PoS journal to a different currency than the company currency.
* Create a product with a standard price > 0.
* Create a pricelist that uses the standard price as a base price. (e.g. price = standard price * 2)
* Add this product to a PoS order
> Observation: The price is not correctly computed according to the
  pricelist, because the standard price was not converted to the PoS currency.

Why the fix:
------------
We just make sure to convert the standard price of the products when loading the products in the PoS session the same way as we do it for the list price.

opw-5124388

Forward-Port-Of: odoo/odoo#244147
Forward-Port-Of: odoo/odoo#241168

Original PR description

**Issue**
When customizing the *Sales: Order Confirmation* mail template, a
validation error appeared if the `website_sale` module was not installed.

**Steps to Reproduce**
1. Go to *Settings → Technical → Email Templates*
2. Open *Sales: Order Confirmation*
3. Make inline changes and save each time
→ A validation error is raised.

**Root Cause**
The template referenced `website_id` on `sale.order`, which only exists
when the `website_sale` module is installed. QWeb pre-evaluates
expressions inside `<t t-if="...">` blocks, so even with
`hasattr(object, 'website_id')`, the engine still tried to access
`object.website_id`, causing the crash.

**Fix**
Guard all `website_id` usages with explicit checks:
`hasattr(object, 'website_id') and object.website_id`, ensuring safe
evaluation when the field is missing.

opw-5180725

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

Forward-Port-Of: odoo/odoo#233825

Original PR description

As runbot faketimes test fail because the usage of dynamic dates

now the test uses freeze_time

Task#5717031

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

Forward-Port-Of: odoo/odoo#244540

Original PR description

Clicking on an odoo link in the chat window will take the user to the related page in odoo. However, in mobile view, the chat window remains unfolded and covers the entire page, so the user can't see the newly opened page below the chat window unless they fold the chat window.
This change fixes this by folding the chat window in mobile view when clicking an odoo link inside the chat window.

task-4762503

Forward-Port-Of: odoo/odoo#244549
Forward-Port-Of: odoo/odoo#208440

Original PR description

This commit rearranges the UBL test files' subfolder to be one level higher, from `export/bis3/be` to `export/bis3/invoice/be`, in preparation for supporting different move formats and for better ignore schema support.

task-4891206

Forward-Port-Of: odoo/odoo#244665

Original PR description

Before this commit, the `printer_interface_L` and `printer_driver_L` shared a single `cups.Connection` instance guarded with a `Lock`. This meant that while the interface for checking for new printers (which can take 10-15 seconds), all printers were being blocked from printing until it was finished.

After this commit, each driver creates its own `cups.Connection` and `Lock`. This means they should never block each other, and prevents long pauses when trying to print.

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

Original PR description

Before this commit, the 'domain' engine was never batched: one expression to evaluate caused one SQL query to be run just for it. With this commit, we group domains that could be evaluated together.

Essentially, when we have domains targetting the same many2one field of account.move.line (typically account_id, with conditions like 'account_id.code' or 'account_id.account_type'), we run only one SQL query for all of them, targetting all the move lines according to the report filters. Then, we iterate on its result for each domain to evaluate. When iterating over the results, we filter the ones we keep by searching separately on each traversing model (in our example, account.account), to isolate the ones that are actually targetted by each expression.

Tested on our prod. With this, opening the Generic Balance Sheet goes from 1min 35s to 36s.

opw-5130725

Forward-Port-Of: odoo/enterprise#101725

Original PR description

When an employee submits an expense and assigns a manager, an approval activity is scheduled.
However, email notifications are now disabled to avoid spamming the assigned managers.

* Prevent notifying the expense manager when expense state changes.

* Email 'Next expense is waiting your approval' is scheduled to be sent
  to the manager once a week if the manager has any expenses left to
approve.

task-4676396

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

Forward-Port-Of: odoo/odoo#210614

Original PR description

…s args

See https://github.com/odoo/o-spreadsheet/commit/6533266efa

Task: 5095364

Original PR description

Before the commit 8b118a7, the search of the documents to update has been limited and ordered.

With the actual domain the records to update will be most of the time the same because is not being updated.

To fix this issue we force to update it.

OPW-5368047

Forward-Port-Of: odoo/enterprise#103272

Original PR description

Microsoft calendar sync can fail in slower environments due to a fixed 3s timeout for Graph requests triggered after commit.

See community changes for details.

Forward-Port-Of: odoo/enterprise#104916

Original PR description

This commit rearranges the UBL test files' subfolder to be one level higher, from `export/bis3/be` to `export/bis3/invoice/be`, in preparation for supporting different move formats and for better ignore schema support.

task-4891206

Forward-Port-Of: odoo/odoo#244665

Original PR description

**Steps to reproduce:**
- Use a Belgian company
- Create a Belgian contact with "EU Standard (Peppol Bis 3.0)" as eInvoice format
- Create an invoice for that customer with a product using "Pack of 6" as unit of measure
- Confirm the invoice
- Send it to Peppol

**Issue:**
The validation of the invoice fails with the following error: "[BR-CL-23]-Unit code MUST be coded according to the UN/ECE Recommendation 20 with Rec 21 extension"

**Cause:**
The UNECE code used for "Pack of 6" UoM is "HD".
"HD" is a correct UNECE code for "Half Dozen".
However, it is not part of the subset of codes accepted by Peppol.

opw-5463212




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

Original PR description

Issue:
`_check_create_documents` is called in 'hr_payroll' but only defined in 'documents_hr_payroll'

Solution:
Create a new method that will be redefined in 'documents_hr_payroll' to call `_check_create_documents`

opw-5213979

Original PR description

When sending an invoice to SInvoice (Viettel), the API raises an `INVALID_DECIMAL_POINT_TAX_MONEY` error if the tax amount contains excessive decimal places (e.g., 100.02999999999997).

This occurs because the tax amount is currently calculated using simple subtraction (`total - subtotal`). Due to standard floating-point precision issues, this can result in unrounded values that the API rejects.

The tax amount calculation is now updated to explicitly use the currency's rounding method, ensuring the value is accepted by SInvoice.

task-[5484845](https://www.odoo.com/odoo/project/967/tasks/5484845)

Forward-Port-Of: odoo/odoo#244647

Original PR description

Steps to reproduce the bug:
- Create a storable product P1 with the following BoM:
    - Create a new operation OP1

- Create a manufacturing order to produce one unit of P1
- Confirm the manufacturing order
- Log in as Mitchel (admin) and start OP1
- Log in as Marc (demo) and also start OP1
- Click on Pending

Problem:
Both “mrp.workcenter.productivity” records are stopped, instead of stopping only the one linked to

The `button_pending` method was stopping productivity records for all employees linked to the work order.

opw-5453752

Forward-Port-Of: odoo/enterprise#103553

Original PR description

## Description:

Add some shortcuts

Task: [5231802](https://www.odoo.com/odoo/2328/tasks/5231802)

## review checklist

- [ ] feature is organized in plugin, or UI components
- [ ] support of duplicate sheet (deep copy)
- [ ] in model/core: ranges are Range object, and can be adapted (adaptRanges)
- [ ] in model/UI: ranges are strings (to show the user)
- [ ] undo-able commands (uses this.history.update)
- [ ] multiuser-able commands (has inverse commands and transformations where needed)
- [ ] new/updated/removed commands are documented
- [ ] exportable in excel
- [ ] translations (\_t("qmsdf %s", abc))
- [ ] unit tested
- [ ] clean commented code
- [ ] track breaking changes
- [ ] doc is rebuild (npm run doc)
- [ ] status is correct in Odoo

Original PR description

Steps to reproduce:
1. Go to Website -> Edit Mode.
2. Drag and drop a "Contact Us" form.
3. Add two fields:
   - selection field (e.g. "Author")
   - text field.
4. Edit the text field's visibility and select comparator
   "Contains" or "Doesn't Contain".
5. Try selecting multiple values (e.g. "Mitchell Admin" and
   "Marc Demo").
6. Only one value can be selected, behaving like equality checks.

Before this commit, visibility rules using the "Contains" or
"Doesn't Contain" comparator behaved like equality checks. Users
were unable to select multiple values when configuring visibility
conditions, even when the dependency field supported multi-value
logic (select, checkbox, radio).

This commit adds support for choosing multiple values when the
comparator is "Contains" or "Doesn't Contain". Visibility now
evaluates correctly for dependency fields of type select, checkbox
or radio.

task-4203938

Original PR description

This task improves the user experience in the signature thank you dialog by modernizing its layout, reducing button sizes, truncating long labels, and formatting dates in a more readable way.

task-5408501

Original PR description

Task: 5502875

Original PR description

When two tables are linked in the pos, we would like to sum the guests.

Here an example :

If Table 1 has two guests and Table 2 has three guests, then Table 1&2 will have five guests.

task: 5490906

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

Forward-Port-Of: odoo/odoo#243726

Original PR description

When trying to create a consolidated invoice in the POS from multiple orders, if any of them would not be valid (i.e. invoice already generated, or order still in draft), then Odoo would throw an error and not do anything.

Now the orders for which invoices can't be generated will just be ignored, but for the rest of the orders the invoices will be generated as usual. This should make it easier to bulk select and generate invoices only where necessary.

Task-[5491082](https://www.odoo.com/odoo/project/1737/tasks/5491082)

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

Forward-Port-Of: odoo/odoo#243851

Original PR description

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

Original PR description

Adds a warning banner to the return kanban view, when the user's active companies do not match the companies on the return.

task-5213029

Original PR description

**Steps to reproduce:**
- Go to Event module
- Go to an open event
- Register for the event
- Go to the Attendees of the event
- On the attendee record, click `Send by Email`
- The received email shows twice the header and footer

**Issue:**
Encapsulating notification layout was applied with `default_email_layout_xmlid` 
but the main template used is `event_registration_mail_template_badge` which
already has its own header and footer.

**Fix:**
Removed the `default_email_layout_xmlid`

opw-5032767

Forward-Port-Of: odoo/odoo#236667

Original PR description

The goal of this pr was to set the printer type by default as `receipt` when a quick create was done from the "Receipt Printers" category and as `preparation` when it's done in the "Preparation Printers" category, both in `pos.config` and in `res.config`.

Also, in the `pos.printer` form view, for a preparation printer, products categories are now required when creating a printer to avoid user oversights.

And, a quick fix to make the default receipt printer as required, under the "Receipt Printers" category in the `res.config`

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

Forward-Port-Of: odoo/odoo#242780

Original PR description

The code of the payment provider is not relevant to the test_ecommerce_paid_order_is_hidden_in_pos test, and pos_sale doesn't have payment_custom in the dependencies. It caused tests to fail so I removed it.

Runbot Build Error-233461

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

Forward-Port-Of: odoo/odoo#232638

Original PR description

see https://github.com/odoo/odoo/pull/244983

Original PR description

**Current behavior before PR**:

The "Day of Week" group by in the Live Chat report always treats Sunday as the start of the week, ignoring the "First Day of Week" configured in the user's language settings.

**Desired behavior after PR is merged**:

"Day of Week" group by now correctly takes into account the user's configured "First Day of Week", as set in their language settings.

**task**-[4808640](https://www.odoo.com/odoo/project.task/4808640)

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

Forward-Port-Of: odoo/odoo#243503
Forward-Port-Of: odoo/odoo#213307

Original PR description

When sending an invoice to SInvoice (Viettel), the API raises an `INVALID_DECIMAL_POINT_TAX_MONEY` error if the tax amount contains excessive decimal places (e.g., 100.02999999999997).

This occurs because the tax amount is currently calculated using simple subtraction (`total - subtotal`). Due to standard floating-point precision issues, this can result in unrounded values that the API rejects.

The tax amount calculation is now updated to explicitly use the currency's rounding method, ensuring the value is accepted by SInvoice.

task-[5484845](https://www.odoo.com/odoo/project/967/tasks/5484845)

Forward-Port-Of: odoo/odoo#244647

Original PR description

**Current behavior before PR:**

Steps to reproduce:

- Create 3 columns using powerbox
- Convert it into 4 columns
- Press ctrl + z to make it 3 columns
- Convert it into 4 columns again using powerbox

Notice that column structure is broken. This happens because after undo operation, in `changeColumnsNumber` the regex replaces column div className incorrectly leading to invalid colund structure.

**Desired behavior after PR is merged:**

This PR ensures that column structure doesn't break.

task-5468578





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

Forward-Port-Of: odoo/odoo#242500

Original PR description

In 'save_edited_profile()', we check that the user can edit his country_id if he tries. As from saas-18.4, a new helper '_can_edit_country()' is available. This commit uses that helper to perform the check.

Follow-up of #239789 

Task-5331916

Forward-Port-Of: odoo/odoo#244795
Forward-Port-Of: odoo/odoo#244694

Original PR description

### Steps to reproduce:

- In the settings enable "Rental Transfers"
- Create a storable and rentable product P
- Create and confirm a rental order for 1 unit of P
- Change the rental period to 10 days in the future
#### > The rental tranfers were not updated accordingly

### Cause of the issue:

Nothing is currently implemented to reschedule the rental transfers.

### Fix:

We somewhat mimic the reschedule purchase behavior: https://github.com/odoo/odoo/blob/6ca34a0f5347e0611cde95453119dda8b40fa589/addons/purchase_stock/models/purchase_order_line.py#L98-L101
But we rely on the order itself rather than its order lines since the `start_date` and the `return_date` are related fields so that no `write` is triggered when the order is rescheduled:
https://github.com/odoo/enterprise/blob/96a80f583a0ca502ff06bc05d03775c76c6a7537/sale_renting/models/sale_order_line.py#L18-L19

opw-5158508

Forward-Port-Of: odoo/enterprise#103602
Forward-Port-Of: odoo/enterprise#101334

Original PR description

The standard price of the products were not converted to the currency of the PoS journal, which could lead to issues when creating pricelist items based on the standard price.

Steps to reproduce:
-------------------
* Change the currency of any PoS journal to a different currency than the company currency.
* Create a product with a standard price > 0.
* Create a pricelist that uses the standard price as a base price. (e.g. price = standard price * 2)
* Add this product to a PoS order
> Observation: The price is not correctly computed according to the
  pricelist, because the standard price was not converted to the PoS currency.

Why the fix:
------------
We just make sure to convert the standard price of the products when loading the products in the PoS session the same way as we do it for the list price.

opw-5124388

Forward-Port-Of: odoo/odoo#244147
Forward-Port-Of: odoo/odoo#241168

Original PR description

When accessing the API documentation endpoint (`/doc`), the server could crash with an Internal Server Error if the database contained ir.model records for models that are not loaded in the current registry.

Steps to reproduce:
1. Insert a record into `ir_model` with `model='ghost.model'` and `state='base'`.
2. Open `/doc`.
3. The server raises a `KeyError: 'ghost.model'`.

Root Cause:

The `/doc` endpoint iterates over all records in `ir.model`. For each record, it attempts to resolve the Python class using `self.env[ir_model.model]` to check access rights. If a model exists in the database with `state='base'`, Odoo expects it to be defined in the Python source code and does not generate it dynamically. If the corresponding Python class is missing (e.g., from an old module), it is never added to the registry, causing the lookup to fail with a `KeyError`.

opw-5401782

Forward-Port-Of: odoo/odoo#241483

Original PR description

Currently, when a user links a chart to an odoo datasource, the sidepanel is not updated properly when the user tries to select a datasource from the same type as the one already selected.

How to reproduce:
- In a spreadsheet, insert a chart and a list datasource
- duplicate the list datasource
- in the chart sidepanel, select list#1 as link
- now try to select list#2

-> the model update the link to list#2 but the interface still shows list#1.

Task-5725964

Forward-Port-Of: odoo/enterprise#104887

Original PR description

Currently, an error occurs when the user opens the Gantt view.

**Steps to Reproduce:**
 - Install `timesheet_grid` without demo data.
 - Go to `Settings` and enable `Project Stages`.
 - Go to `Projects` and switch to the `Gantt view`.

`UnboundLocalError: cannot access local variable 'project' where it is not associated with a value`

This error occurs because, in [this commit], line [1] is mistakenly placed outside the loop. If self has no records, project is not defined, and accessing project.date_start raises an error.

This commit moves the line inside the loop.

[1]: https://github.com/odoo/enterprise/blob/34feeda7d0835d8c65d91493314133b8e83610d1/timesheet_grid/models/project_project.py#L50

[this commit]: https://github.com/odoo/enterprise/commit/c3296d1441400d20e3815207baa1188b5cb8fd93#diff-59e7d75aff5c1e890cd536834137eac5cd3ad185cb45ee1e157be15402cbc90fR50

sentry-7204644855

Forward-Port-Of: odoo/enterprise#105009

Original PR description

Issue: 
when using the server action 'Import Bank Statement' the code
would not filter on the currently selected company for choosing the
journal on which to encode the bank statement and simply take the first
result. Because the server action is running with sudo rights, in a
multi-company environment more then one journals are found and the
selected one is often wrong.

Solution: filter on company during the selection of the journal.

Note: a test was added in which we run the function with sudo rights
to ensure an error is raised when the journal does not exist on the 
currently selected company, even if it is present on another company.

Task-5494685

Forward-Port-Of: odoo/enterprise#105003
Forward-Port-Of: odoo/enterprise#104326

Original PR description

In the form view of invoices and bills, if the currency is changed to an inactive one, an option to activate it from the form view was available, but when the button is pressed the front-end doesn't receive the new data related to the currency which resulted in unexpected errors when trying to view the invoice/bill or the list of invoices/bills 
task-5412003

Forward-Port-Of: odoo/odoo#240086

Original PR description

Reduce amount of LOCs to define dark theme version of message bubble colors, to match with the shape of how this is defined in white theme.

While the intent of the change is just simpler LOCs, the visual in dark theme has subtle changes:
- bubble colors are very slightly more saturated in dark theme
- bubble have more visible border, giving more a 3D look

Before

<img width="778" height="639" alt="before" src="https://github.com/user-attachments/assets/4f4aa3e3-9e2f-44bf-9437-665203831103" />

After

<img width="771" height="642" alt="after" src="https://github.com/user-attachments/assets/1c4f4b84-0eb0-45ce-bda3-3a849e93d49d" />

Original PR description

Added a new module to support Finnish Intrastat compliance by generating CSV declarations compatible with the Finnish Customs service.

This Includes:
- Export arrivals and dispatches reports in CSV format (bundled in ZIP).
- Configure agent VAT for arrivals when filed via an agent.
- Wizard to download and submit periodic Intrastat reports.

task-5049047

Original PR description

**Steps to reproduce**
- Install `hr_work_entry_attendance`
- Delete one of the overtime rules from the "Default Ruleset", e.g. "Employee Schedule Rule"
- Upgrade the `hr` module
- Traceback: `psycopg2.errors.CheckViolation: new row for relation "hr_attendance_overtime_rule" violates check constraint "hr_attendance_overtime_rule_if_paid_work_entry_type_defined"`

**Cause**
The `_if_paid_work_entry_type_defined` constraint added by the `hr_work_entry_attendance` module on overtime rule records will fail when re-creating an overtime rule record when upgrading another module than `hr_work_entry_attendance`, since the module is not loaded and we don't get a default value for the `work_entry_type_id` field.

**Fix**
Since the ORM cannot manage that, disable forcecreate for these records.
Related: https://github.com/odoo/enterprise/commit/f935e62bae7f204ea3f6db8f08b173bdf011c0d2

opw-5428542

Original PR description

Bug
===
Since 22446368503fadc0e0bf459dd3c8ab8b8f6624b0 , we use a mail template to share access, but in e3e8d6a6b9423feae4dd88978065bd8799031b2b , we added the link in the standard notification process (because it was done in 18.0).

Task-5242208

Original PR description

Safety measure to prevent hidden bugs and data corruption which can happen when multiple schema are used in PostgreSQL.

Description of the issue/feature this PR addresses:
Related to:
- PR  #243833
- OPW [opw-5495025](https://www.odoo.com/my/tasks/5495025)
- issue reported earlier: #97891




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

Original PR description

The status banner widget expected the state to be equal to `waiting_validation` once the document was successfully digitized. But when auto-post is used on vendor bills, the state will skip directly to `to_validate` as the bill is posted right after the digitization. It can even be moved to `done` if the validation cron has time to run before the update of the banner.

task-[5480954](https://www.odoo.com/odoo/49/tasks/5480954)

Original PR description

It prevents hidden bugs when multiple schemas are used in PostgreSQL

This was mentioned in:
- PR odoo/odoo#243967

Original PR description

Before this commit, the user's live chat expertise were always returned as part of `_init_store_data`. However, this led to a warning in portal tours because the expertises are inserted into the store while the live chat models are not loaded (they are not needed).

We shouldn't return useless data. This commit fixes this issue by fetching the data when they will be needed (i.e. when the discuss app is opened with a live chat user).

runbot-234137

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

This PR fixes some issues with the voice transcription feature that were causing poor quality in the transcription.

Among the changes:
- Removing filtering on the input audio in the `vad_audio_recorder.js`
- Reducing buffer size in the `vad_audio_processor.js` to send data more
frequently. Hence, avoiding to send data during the VAD silence cutoff.
- Changing the model to `whisper-1`.

task-5788331

Original PR description

Follow up of 682d6ec1ddb825674999e0db1fc0cc48c3be67c5 where I forgot to add the client-side data upgrade

Task-5477426


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

Original PR description

*=html_builder

This PR introduces the following changes:
- Add `.accordion-item` selector in the `AnchorPlugin`.
- Expands the list of titleEls selectors to include `.h1-fs, .h2-fs, .h3-fs, .h4-fs, .h5-fs, .h6-fs, .display-1-fs, .display-2-fs, .display-3-fs, .display-4-fs, .base-fs, .o_small-fs`.
-  Enhances the "AnchorSlide" interaction by adding the "handleAccordionAnchor" method, called in "animateClick" and "setup"
to automatically scroll to and expand accordion items. The method uses the `show()` function from bootstrap `Collapse` component, which efficiently manages the expansion of required accordion item and collapse the rest.

task-5065165

Original PR description

Archived returns are ignored when manually creating returns, allowing a new return to be created for the same period without reactivating or overwriting the archived one.
Also a test case has been added for the same

task-5440965

Original PR description

Selecting an operation in the Overview makes it the 'show case' and first in the workcenter's operations list.

However, acting on the workorder (adding a by-product for example) moves it to another position in the list.

This because defineRelevantRecords wrongly uses record.'id' to sort recordsAlreadyInCache (internal data like 'datapoint_<n>' not present in the cache that contains record identifiers).

Using the real record identifier 'resId' corrects the sorting operation.

We also want the 'show case' workorder selected in the Overview to stay on top when using pagination (not for all pages, only the first one).

task: 5028095

Original PR description

The `Opening thread with needaction messages should mark all messages of thread as read` text composer test ensures that opening a channel marks the related inbox messages as read.

However, this test can fail in a non-deterministic fashion. There are two flows that can mark inbox messages as read: fetching the messages or a manual request after opening the channel.

The test expects the rpc to be issued, but if the messages are fetched before, it won't happen thus making the test fail.

This commit awaits the initial fetch to prevent this issue. As a bonus, the second flow is also tested.

runbot-238360

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

## Description

Before this commit:
- In the selection global filter side panel, field matching was shown immediately,
even when the model and field were not selected.
- Without a model, field matching cannot be configured correctly,
so showing it early had no meaning.
- This behavior was inconsistent with relational global filters.

After this commit:
- Field matching is displayed only after the user selects both model and field.
- Once configured, users can set up field matching as expected,
similar to the relational global filter side panel.

Task: [5477251](https://www.odoo.com/odoo/project/2328/tasks/5477251)

Original PR description

This error occurs when clicking the `Code History` button in Server Action.

Steps to reproduce:
- Search `Server Actions` > Open any server action
- Change `Code` and Save > Click `Code History` button

Traceback:
`AttributeError: 'bool' object has no attribute 'upper'`

This error occurs when the `Code History` button is clicked and, at that point, the user’s timezone is `False` because it is not set in the user’s calendar.

[1]- https://github.com/odoo/odoo/blob/54681272e9f00a171fe49f690979e2a8353ff5fb/odoo/addons/base/models/ir_actions.py#L515

sentry-7167683304

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

Original PR description

Since this fix: ba24b48 , a default empty document contains `<Note>No xml</Note>` was created when posting bills. However, the `l10n_co_dian.report_invoice_document` template attempts to parse this document for DIAN values. Because these values are missing from the empty document, a traceback occurs.

In this commit, we fallback to standard template when the empty document exists.

opw-5246912

Original PR description

**Steps to reproduce:**
* Install `l10n_co_dian` and `accounting` modules.
* Go to **Accounting → Configuration → Settings** and enable DIAN demo mode under `Colombian Electronic Invoicing` by disabling `test mode`.
* Create an Invoice.
* Select a Colombian customer and add products.
* Fill in the **Terms and Conditions** field (e.g., “Payment due in 30 days”).
* Confirm the invoice and generate the electronic invoice XML.

**Observed behavior:**
* The `<cbc:Note>` tag only contains **CUFE calculation data**.
* The **Terms and Conditions** text is missing from the XML.

**Cause:**
* The `'cbc:Note': None` ovrride the value of Note tag which has value of
  invoice.narration. 
ref : https://github.com/odoo/enterprise/pull/87598/changes#diff-2548895191bf05af735ebfc332b3f3f2db9d039630101720ee72feb7b65fa8fcR532

**Fix:**
* removed the `'cbc:Note': None` which overrides the value of the note tag.

opw-5488663

Original PR description

Problem:
Table cells had extra space because the last element (e.g. a `<p>`) kept its bottom margin. This caused the cell content to appear misaligned vertically.

Solution:
Remove the bottom margin on the last element inside table cells. This is a backport of 3048f1a2447d1d5089defa055c858adb1e915c91.

Steps to reproduce:
- Website.
- Add a table in the footer.
- Add text in a cell.
- Select "Paragraph" as block from the toolbar.
- Align the cell content.
- Observe the content is not vertically aligned.

opw-5412426

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

Original PR description

### [FIX] web: allow 'uuid' in non-secure contexts

Before this commit, the `uuid` string helper crashed when used in non-
secure contexts. This was due to it using `crypto.randomUUID()`, which
is only available in secure contexts.

Although discouraged, it should be possible to run Odoo in these
contexts, and as such the function has been changed to use
`crypto.getRandomValues()`.

There is no test, as the CI runs in secure contexts anyway, and the
`uuid` function itself is already thoroughly tested.

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

Original PR description

Apparently somewhere in the datetime patterns the space between time and A/P mark has been updated from a narrow non-breaking space to a regular space.

Make the code cross-version compatible.

Original PR description

Before:
SInvoice was stripping newlines from the `itemName` field. Since we were directly using `line.name` (which contains a `\n` between product name and description), the content ended up concatenated without any separation.

After:
Now we replace the newline with a space before sending the value, so the name
and description remain readable once processed by SInvoice and set
limit to 500 characters as per API specs.

task-5498120

Forward-Port-Of: odoo/odoo#243994

Original PR description

Steps to reproduce:
1. Set network speed to 3G
2. Create website Page from the systry new menu
3. click on edit button You'll face the traceback.

The website editor could try to open before the iframe finished loading, leading to non-deterministic behavior. This commit ensures the editor initializes only after the iframe load event, making the edit action consistent and reliable.

Erlier fixed was not covering the all the cases. PR: https://github.com/odoo/odoo/pull/238054

runbot-233039

Forward-Port-Of: odoo/odoo#243256

Original PR description

For export invoices, the total invoice value in the eWaybill JSON did not include reverse charge amounts for GST, leading to a mismatch with the value shown in Odoo and the eWaybill generated by the Indian government system.

This commit adjusts the JSON computation to include the reverse charge amounts in the total invoice value for exports, aligning it with the government-generated eWaybill, while preserving the existing reverse charge flow.

task-5068199

Forward-Port-Of: odoo/odoo#243802
Forward-Port-Of: odoo/odoo#241852

Original PR description

### Steps to Reproduce : 

- Open To-Do and type some text.
- Place the cursor at the start of the block.
- Insert a table. (e.g.: /table)
- The table appears after the text instead of before it.

### Purpose of this PR:

- Table insertion logic was previously duplicated inside TablePlugin, where it tried to manually split text and inline nodes before inserting the table. However, this responsibility is now correctly handled by `DomPlugin.insert()`, which already:
  - deletes the current selection if needed.
  - splits text and inline nodes safely.
  - handles block boundaries and unsplittable elements.
  - normalizes the DOM after insertion.
  - places the cursor at a valid position.

task-5480759

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

Forward-Port-Of: odoo/odoo#244567
Forward-Port-Of: odoo/odoo#243242

Original PR description

ref - https://github.com/odoo/enterprise/commit/ea7893a978c408e5d4437070ae7a6c7a7fbf7167

Forward-Port-Of: odoo/enterprise#104882

Original PR description

When we register payments for a list of journal entries, the `account.payment.register` wizard computes batches and sometimes merge them together.

For instance, this allows to create a single payment if there is an outbound (a bill to pay) and an inbound (a refund to receive) payment to the same bank for the same partner. Instead of creating two payments of -1000 and +500, we only create one of -500.

Currently, this mechanism does not always work. That's because the `batch_key` used to decide whether to merge or not refers to a value that is not updated in the loop.

Related ticket: opw-5401372

Original PR description

**Current behavior before PR:**

In editor's custom gradient picker, if `#FFFFFF` is picked from the very top of picker area, the color slider is reset to color `red`. This happens because when moving picker pointer to the top of area, `selectedColor` prop is updated to `#FFFFFF`, which calls `onWillUpdateProps` callback. As result, `convertRgbToHsl` sets hue value 0 for `#FFFFFF`, setting color slider to red.

**Desired behavior after PR is merged:**

This commit ensures that in `onWillUpdateProps` callback, `setSelectedColor` should not get called if `newSelectedColor` is the same as `this.colorComponents.cssColor` to prevent updating UI twice while picking the color.

task-5170041




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

Original PR description

## Versions
18.0+

## Issue
On iOS devices, when submitting a product review with a custom star rating, the selected value would revert to the default (4 stars) before submission.

## Steps to reproduce
*On a laptop*
- Open Editor mode on a product eCommerce page:
  - Select any product element (e.g. click on the price);
  - Activate customer ratings and save.

*On a physical Apple mobile device (iPhone or iPad) or on an iOS emulator via XCode (only on MacOS)*
- Go to the product's eCommerce page:
  - Move down to the "Customer Reviews" section and un-toggle it:
    - Write down a review;
    - Click on any star rating but 4;
    - Send.

## Cause
`mouseleave` event is triggered before the rating is saved and resets the rating to the default 4-star one.

## Solution
Only trigger `mouseleave` event on devices handling them correctly and post the number of visible stars on the form.

opw-5142682

Original PR description

When the gevent server is under high load, the time required to acquire a cursor and fetch notifications increases. This causes notifications to accumulate, leading to larger payloads.

Serializing these large payloads using the standard json library becomes a bottleneck. In a gevent environment, this monopolizes the event loop, delaying the processing of other greenlets.

This commit introduces optional support for `orjson`. If installed, it is used to significantly speed up JSON encoding, freeing up the event loop.

Using `orjson` increases the throughput by ~20% under high load.

Original PR description

Backport of https://github.com/odoo/odoo/pull/244094

Before this commit, when message list failed to load, it just displays a "Ann error occurred" generic message with a retry button.

This assumes that error happens rarely and when so this is temporarily. However some errors are persistent and it's frustrating to have no clue on why there's error or what may have caused it.

This commit shows the `Error.toString()` from fetch message RPC failure on UI, so that there's a clue on the reason the fetch of messages failed.

Before / After
<img width="305" height="67" alt="Screenshot 2026-01-20 at 15 10 38" src="https://github.com/user-attachments/assets/34c546df-71e6-4055-9f85-8d85a9c89b35" /> <img width="334" height="100" alt="Screenshot 2026-01-20 at 15 09 07" src="https://github.com/user-attachments/assets/5fadd0b7-7ea0-43ca-8c28-0ac1d33650ff" />