This update moves Odoo's web test pages to the newer testing system and keeps legacy test pages available separately. It also fixes several testing-tool behaviors around clicks, touch events, screen sizing, and sidebar layout, helping teams validate web changes more reliably.

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

Updates the website editor's automated checks to better catch issues during page editing. This helps reduce the chance of regressions reaching users and supports more reliable website publishing workflows.

TODO
runbot-60056

The /help command in Discuss now includes canned response guidance, matching the behavior users already had in live chat. This makes the feature easier to discover and use wherever canned responses are available.

Since the canned response settings is introduced in Discuss,
the usage of canned responses is not limited to livechat only,
so that the /help message should be available in the Disucss as well.

after:
![1948421007](https://github.com/user-attachments/assets/ff9a3cb6-c734-4f43-a876-632041a97f30)


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

Odoo now handles mailing list contacts without a name when an email fails to send. This prevents a traceback when users open the contact record after a failed mailing, improving reliability for mass mailing workflows.

Steps to reproduce:
---
1. Install mass_mailing
2. Create a wrong outgoing mail server
3. ip 127.0.0.1 port 1234
4. Create a mailing list
5. Create a mailing list contact without name
6. Make the contact join the list
7. Create a mailing, set the new mailing list
8. Click on send > "1 email(s) not sent."
9. Open the mailing list contact
10. Traceback

Cause of the issue:
---
Caused by: https://github.com/odoo/odoo/commit/5102328c3dd6e4e751ca8f906e7bd16e190fc386 
`this.originThread?.name` can be `False` instead of `Undefined`

opw-4054564

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

If we have two bills with the same bill ref and two different partner, one with NIF and the other without it, the schedule action to process SII response might fail since the code expect a NIF in the SII response when there is not (bill with partner without NIF). Technical example: ```py >>> partner_info # Candidate invoice in odoo {'IDOtro': {'ID': 'NO_DISPONIBLE', 'IDType': '06', 'CodigoPais': 'ES'}} >>> respl_partner_info # SII response {'NIF': '12345678K', 'IDOtro': None} ``` This

If we have two bills with the same bill ref and two different partner, one with NIF and the other without it, the schedule action to process SII response might fail since the code expect a NIF in the SII response when there is not (bill with partner without NIF).

Technical example:
```py
>>> partner_info # Candidate invoice in odoo
{'IDOtro': {'ID': 'NO_DISPONIBLE', 'IDType': '06', 'CodigoPais': 'ES'}}
>>> respl_partner_info # SII response
{'NIF': '12345678K', 'IDOtro': None}
```
This causes a rollback and no bills at all are processed in Odoo's side.

Steps to reproduce:
1/ Create a l10n_es company with l10n_es_edi_sii in test mode
2/ Create a bill with a bill reference 10001, some lines (ex: negative lines)
     that will trigger an error from SII and a partner with a NIF
3/ Copy the partner and remove the NIF
4/ Copy the first bill, keep the same bill reference and change the partner to
     copied one
5/ Post both bills
6/ Trigger the schedule action "EDI : Perform web services operations" => Traceback with
ValueError: <class 'AttributeError'>: "'NoneType' object has no attribute 'ID'" while evaluating

Now, a default value is set when the key is not found in respl_partner_info.IDOtro .

opw-4102638

Forward-Port-Of: odoo/odoo#177902

Currently, when adding product rewards to an order, you are rewarded with the maximum amount of products you can get with you current points. If you change the quantity of the reward product, the reward lines does not update. Steps to reproduce: ------------------- * Go to the **Point of sale** App * Open Shop session * Select a customer that has plenty of loyalty points * Put any product in the order * Add the reward `Simple pen` (you'll havelike 230 of them) * Try changing the reward

Currently, when adding product rewards to an order, you are rewarded with the maximum amount of products you can get with you current points. If you change the quantity of the reward product, the reward lines does not update.

Steps to reproduce:
-------------------
* Go to the **Point of sale** App
* Open Shop session
* Select a customer that has plenty of loyalty points
* Put any product in the order
* Add the reward `Simple pen` (you'll havelike 230 of them)
* Try changing the reward quantity to 1
> Observation: The quantity of the simple pen changes to 1 but the negative reward line still shows 230. Thus, the order can have a negative amount since 229 pens are still being deducted from the order even though they are not present.

Why the fix:
------------
This commit https://github.com/odoo/odoo/commit/de45ff3c9f23decdab176bc1511b3356d19844a8 passes the quantity and cost (in points) to the `_applyReward` function. This was done because when recomputing reward lines, if two lines came from the same reward, the quantity would be merged even though they would not apply on the same product.

In our case, this causes problems as we are using the function `_getRewardLineValuesProduct` to update the reward quantity but the quantity (230) is given as an argument and is then used as the quantity to set.
https://github.com/odoo/odoo/blob/775827b8f7fa95f2afd77a9b42d6cd8e436ea690/addons/pos_loyalty/static/src/overrides/models/loyalty.js#L1548-L1566

`args["quantity"] || freeQuantity` will always use `args["quantity"]` if given, bypassing the maximum quantity that is available to give.

`freeQuantity || args["quantity"]` will never use `args["quantity"]`.

Since we do not want to reward more than what is available, we add the arguments inside the `Math.min` function.

opw-4103833

Forward-Port-Of: odoo/odoo#178805

Current behavior before PR: 1. When we attempt to paste an H1 element into a P element, the H1 element gets converted to a P element. 2. When pasting from GDocs, nested UL or OL is a direct child of its parent UL or OL, rather than being child of LI with class `oe-nested`. 3. Copy/pasting multiple paragraphs into a list does not convert it to list. 4. When pasting content that begins with a list and includes other tags below it into a new list, only the list is pasted, resulting in a loss

Current behavior before PR:

1. When we attempt to paste an H1 element into a P element, the H1 element gets converted to a P element.
2. When pasting from GDocs, nested UL or OL is a direct child of its parent UL or OL, rather than being child of LI with class `oe-nested`.
3. Copy/pasting multiple paragraphs into a list does not convert it to list.
4. When pasting content that begins with a list and includes other tags below it into a new list, only the list is pasted, resulting in a loss of the other content.
5. Copy/pasting one list over another bullets does not get transformed.
6. When copying a checklist from Google Docs, the check options are pasted as images.

Desired behavior after PR is merged:

1. When we attempt to paste an H1 element onto a P element, the H1 element will remain as an H1 element.
2. When pasting from GDocs, nested UL or OL are contained within an LI element with class `oe-nested`.
3. Copy/pasting multiple paragraphs into a list gets converted to list.
4. Pasting content with a list and other tags should no longer result in the loss of content.
5. Copy/pasting one list over another bullets get transformed.
6. Check options copied as image from Google Docs will no longer be pasted as images; instead the images should be removed and class `o_checklist` should be add to the closest list.

task-2956048

Co-authored-by: Deependra Solanki <deso@odoo.com>

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

Forward-Port-Of: odoo/odoo#179159
Forward-Port-Of: odoo/odoo#115019

Partners can have multiple Bank accounts in an active database, some being even added automatically on Bank reconciliation. But usually, only some specific accounts that are used for outgoing payments will be marked as "trusted". Currently, when you select a Vendor on a draft Vendor Bill, the first account of the partner is taken, whether or not the account is trusted. This Pr will give priority to the accounts that are trusted. task: 4166740 --- I confirm I have signed the CLA a

Partners can have multiple Bank accounts in an active database, some being even added automatically on Bank reconciliation. But usually, only some specific accounts that are used for outgoing payments will be marked as "trusted".

Currently, when you select a Vendor on a draft Vendor Bill, the first account of the partner is taken, whether or not the account is trusted. This Pr will give priority to the accounts that are trusted.

task: 4166740




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

Forward-Port-Of: odoo/odoo#179365

Steps to reproduce: * install `l10n_mx` * Create a partner * duplicate it * upload an invoice/bill xml with the duplicated partner Issue: A new duplication of the partner will be created Cause: If no partner is found, we will create another one https://github.com/odoo/enterprise/blob/c66a452661c1e5ff9f837e7e1e21e068fec4c124/l10n_mx_edi/models/account_move.py#L2524-L2545 Solution: The VAT should be a sufficiently distinctive criterion to link a partner Ticket [link](https://www

Steps to reproduce:
* install `l10n_mx`
* Create a partner
* duplicate it
* upload an invoice/bill xml with the duplicated partner

Issue:
A new duplication of the partner will be created

Cause:
If no partner is found, we will create another one https://github.com/odoo/enterprise/blob/c66a452661c1e5ff9f837e7e1e21e068fec4c124/l10n_mx_edi/models/account_move.py#L2524-L2545

Solution:
The VAT should be a sufficiently distinctive criterion to link a partner

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

Forward-Port-Of: odoo/odoo#178078

This commit fixes the error that was triggered when trying to assign a responsible user for a picking batch from the kanban view of batches. The error was thrown because the `user_id` field depends on `company_id` field in its domain, which was not existent in the kanban view. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179179

This commit fixes the error that was triggered when trying to assign a responsible user for a picking batch from the kanban view of batches. The error was thrown because the `user_id` field depends on `company_id` field in its domain, which was not existent in the kanban view.

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

Forward-Port-Of: odoo/odoo#179179

Issue : 17.0 When a global discount is applied on a sale order with tax included in the price, the discount was incorrectly calculated based on the tax-excluded price. This resulted in inaccurate discount amounts and incorrect tax calculations. steps to reproduce: - Create a tax with included in price (e.g. 10% incl). - Create a sale order with the 10% incl tax. - Now, apply a global discount (e.g. 10%) Cause : When applying a global discount, the system incorrectly calculates the d

Issue : 17.0

When a global discount is applied on a sale order with tax included in the price, the discount was incorrectly calculated based on the tax-excluded price. This resulted in inaccurate discount amounts and incorrect tax calculations.

steps to reproduce:
- Create a tax with included in price (e.g. 10% incl).
- Create a sale order with the 10% incl tax.
- Now, apply a global discount (e.g. 10%)

Cause :
When applying a global discount, the system incorrectly calculates the discount based on the tax-excluded price rather than the unit price.

Fix :
Ensure the total amount is calculated useing price_unit(price_unit) instead of subtotal.
This corrects the discount application and maintains accurate pricing.

opw-4018841

Forward-Port-Of: odoo/odoo#174678

Steps to reproduce ================== - Go to Sales > Quotation - Open any record - Open studio - Switch to the x2many list view - Insert a new html field - Exist studio - Type some text in the html field - Select a portion of it - Click on the bold button => Nothing happens Solution ======== Don't unselect the current row when clicking inside the editor toolbar opw-4064662 Forward-Port-Of: odoo/odoo#178189 Forward-Port-Of: odoo/odoo#175880

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

- Go to Sales > Quotation
- Open any record
- Open studio
- Switch to the x2many list view
- Insert a new html field
- Exist studio
- Type some text in the html field
- Select a portion of it
- Click on the bold button

=> Nothing happens

Solution
========

Don't unselect the current row when clicking inside the editor toolbar

opw-4064662

Forward-Port-Of: odoo/odoo#178189
Forward-Port-Of: odoo/odoo#175880

We don't need `point_of_sale` module on the IoT Box: we only need configuration files in it. We don't load it anymore to prevent from having error messages on service start. We also added a new alias to simplify pip usage and removed unused pyotp package. Forward-Port-Of: odoo/odoo#179308

We don't need `point_of_sale` module on the IoT Box: we only need configuration files in it.
We don't load it anymore to prevent from having error messages on service start.

We also added a new alias to simplify pip usage and removed unused pyotp package.

Forward-Port-Of: odoo/odoo#179308

Before this commit, copying an automation rule did not copy its actions. After, it will. Task: 4055597 Forward-Port-Of: odoo/odoo#179350

Before this commit, copying an automation rule did not copy its actions. After, it will.

Task: 4055597

Forward-Port-Of: odoo/odoo#179350

### Description of the issue/feature this PR addresses: Wrong account on tax definition. Taxes should not have related payable and receivable accounts. ### Current behavior before PR: VAT 0% Exempt taxes has a payable account, this not valid one and will result on error when creating an invoice with that tax. We resolve the problem by changing the account used on the tax definition with new accounts, one for Sales (Current liabilities) and another for Purchase (Current Aseste), the sam

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

Wrong account on tax definition. Taxes should not have related payable and receivable accounts. 

### Current behavior before PR:

VAT 0% Exempt taxes has a payable account, this not valid one and will result on error when creating an invoice with that tax. We resolve the problem by changing the account used on the tax definition with new accounts, one for Sales (Current liabilities) and another for Purchase (Current Aseste), the same way is made for the VAT 22% and VAT 10%)

### Desired behavior after PR is merged:

Taxes has the proper account and we are able to create invoices/bills with tax 0% without problem

ADHOC ticket 76475 - task 34060

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

Forward-Port-Of: odoo/odoo#170773

In makeAsyncHandler and makeButtonHandler have been modified in commit fcb16a3b1bd373726ffb54f0fbe41fb6d1784769 to remove guardedCatch. However, in both cases, if result is rejected, Promise.resolve(result) will (quite unexpectedly because of the name of the method) be rejected too. Calling finally on this promise will indeed call the callback, but it will still let the exception bubble up, eventually resulting in a second unhandledrejection for the same original exception. With this commi

In makeAsyncHandler and makeButtonHandler have been modified in commit fcb16a3b1bd373726ffb54f0fbe41fb6d1784769 to remove guardedCatch.

However, in both cases, if result is rejected, Promise.resolve(result) will (quite unexpectedly because of the name of the method) be rejected too. Calling finally on this promise will indeed call the callback, but it will still let the exception bubble up, eventually resulting in a second unhandledrejection for the same original exception.

With this commit, we instead call then(callback, callback) on that Promise, so that the rejection is caught and callback is indeed called in both cases.

To reproduce this issue in saas-17.4, raise a UserError in the route /website_sale/should_show_product_configurator and add a Drawer to your cart: the exception message is displayed twice.
This reproduction doesn't work in 17.0 because the promise is a dialog.opened() that crashes and never resolves, masking the issue (but there is a hint of this, because the loading effect is also never removed from the button (meaning that the callback of makeButtonHandler is never called). Many thanks to MCM to help me understand what was happening here.

Forward-Port-Of: odoo/odoo#179512

[FIX] project: restrict access to project in email sent Before this commit, when the `Project Stages` feature is enabled and the user set an email template on a project stage, if the user moves a project to that stage with the email template, an email is sent to the customer (if set on the project) and the customer can click on the project name to see all tasks inside that project even if the project is private. This commit makes sure the project name displayed in the template is only

[FIX] project: restrict access to project in email sent

Before this commit, when the `Project Stages` feature is enabled and the
user set an email template on a project stage, if the user moves a
project to that stage with the email template, an email is sent to the
customer (if set on the project) and the customer can click on the project name
to see all tasks inside that project even if the project is private.

This commit makes sure the project name displayed in the template is
only clickable is the project visibility is 'portal'
(`Invited portal users and all internal users`).

Steps to reproduce:
------------------
1. Install project
2. Go to Project > Configuration > Settings
3. Enable Project Stages feature
4. Set email template to project stage
5. Create a project with a customer set and project visibility is not
   set to "Invited portal users and all internal users".
6. Move the project to the project stage with the email template set.

Current behavior:
----------------
An email is sent based on the email template set but the project name is
clickable to allow the customer to see the tasks of the project in the
portal even if the project is not public.

Expected behavior:
-----------------
The project name should not be clickable inside the email sent when the
project visibility is not "Invited portal users and all internal users".

Close #175396

Forward-Port-Of: odoo/odoo#178260
Forward-Port-Of: odoo/odoo#178171

Following commit https://github.com/odoo/odoo/pull/171765/files# multi-currencies are not supported anymore by our edi engine. Using a currency other than euro leads to an invalid XML file. Steps to reproduce: 1. install Italian E-invoicing 2. make sure your have access to another currency, along with EUR 3. create a partner outside of Europe (e.g. US-based - using USD) 4. create an invoice for that partner 5. confirm + send and print the invoice (generate XML file) 6. go to https

Following commit https://github.com/odoo/odoo/pull/171765/files#
multi-currencies are not supported anymore by our edi engine.

Using a currency other than euro leads to an invalid XML file.

Steps to reproduce:

1. install Italian E-invoicing
2. make sure your have access to another currency, along with EUR
3. create a partner outside of Europe (e.g. US-based - using USD)
4. create an invoice for that partner
5. confirm + send and print the invoice (generate XML file)
6. go to https://www.fatturacheck.it/ to verify the XML
7. Error 2.2.2.5 should be returned

opw-4038850
opw-4129380
opw-4123758
opw-4095910

Forward-Port-Of: odoo/odoo#175996

### Steps to reproduce: - In the settings: - Change the Barcode Nomenclature to Default gs1 - Enable Promotions, Coupons, ... on Point of sale - Create a prodcut with barcode 95412427100283 - Point of Sale > Product > Discount & Loyalty - Create a new discount and change the conditional rule to set your product and a min purchase of 0 - Open a new pos session - Scan the gs1 barcode 0195412427100283 #### > the product is found but the discount is not applied ### Expected behav

### Steps to reproduce:

- In the settings:
  - Change the Barcode Nomenclature to Default gs1
  - Enable Promotions, Coupons, ... on Point of sale
- Create a prodcut with barcode 95412427100283
- Point of Sale > Product > Discount & Loyalty
- Create a new discount and change the conditional rule to set your product and a min purchase of 0
- Open a new pos session
- Scan the gs1 barcode 0195412427100283

#### > the product is found but the discount is not applied

### Expected behavior:

Just as if you scanned the barcode 95412427100283 directly the discount should be applied.

Cause of the issue:

When a barcode is scanned in the pos, the ` _scan` method is called to parse the barcode and to trigger the associated action:
https://github.com/odoo/odoo/blob/775827b8f7fa95f2afd77a9b42d6cd8e436ea690/addons/point_of_sale/static/src/app/barcode/barcode_reader_service.js#L69-L79
This flow use to not update the rewards after a product scanned and was fixed by commit 21392ab when the barcode associated action is `_barcodeProductAction` because fo these lines:
https://github.com/odoo/odoo/blob/775827b8f7fa95f2afd77a9b42d6cd8e436ea690/addons/pos_loyalty/static/src/overrides/components/product_screen/product_screen.js#L105-L107 however, if the code is identified to be gs1
Howecver, if the barcode is identified to be of the gs1 nomenclature it will trigger the `_barcodeGS1Action` which still does not update the rewards.

### Fix:

Inspired by commit 21392ab

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

Forward-Port-Of: odoo/odoo#178600

Loyalty programs discount could be applied on specific products through a domain. When putting a domain with a True or False as a third operand (e.g. ('is_available_in_pos', '=', True)), the PoS was crashing at launch because the domain goes through a json.dumps that changes the Boolean to lower case and then through ast.literal_eval that doesn't accept lower case Boolean. The change is to replace lower case Boolean to upper case Boolean in the domain before the ast.literal_eval. --- I co

Loyalty programs discount could be applied on specific products through a domain. When putting a domain with a True or False as a third operand (e.g. ('is_available_in_pos', '=', True)), the PoS was crashing at launch because the domain goes through a json.dumps that changes the Boolean to lower case and then through ast.literal_eval that doesn't accept lower case Boolean.

The change is to replace lower case Boolean to upper case Boolean in the domain before the ast.literal_eval.

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

Forward-Port-Of: odoo/odoo#175805

Problem: While merging two partners in the contact app using the _update_foreign_keys method, the foreign keys are merged using SQL instead of ORM. The issue is that the partner_share field is computed based on the user_ids field and is stored. If we update using SQL, it will not trigger the _compute_partner_share method, which will set the latest value. Other problems might arise for fields that are computed based on foreign keys updated using SQL during a merge. Steps to reproduce: I

Problem:
While merging two partners in the contact app using the _update_foreign_keys method, the foreign keys are merged using SQL instead of ORM. The issue is that the partner_share field is computed based on the user_ids field and is stored. If we update using SQL, it will not trigger the _compute_partner_share method, which will set the latest value.

Other problems might arise for fields that are computed based on foreign keys updated using SQL during a merge.

Steps to reproduce:

In a new database, create a basic contact (individual, with name and email).
Merge this contact with another contact who has document access (e.g., Marc Demo).
Go to any product page.
Add a log note and tag the new contact.
The contact will receive an email without the "View product" button.

opw-3864317

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

Forward-Port-Of: odoo/odoo#175966

WhatsApp-related timezone handling now relies on standard fields instead of custom logic. This makes event registration messaging easier to maintain while keeping the expected timezone behavior intact.

Timezone fields can be inferred easily from a fixed list of fields.

We add a related field on event registrations so it fits the heuristic, and remove the override to the method that previously defined the path to the timezone field.

task-4095356

Approval request buttons now use adjusted colors to make the workflow easier to understand. This helps users quickly identify the right action and reduces confusion when processing approvals.

Buttons color have been adjusted to enhance the flow's understandability.

task-3987625

This update renames a field used in India GSTR point-of-sale reporting to align with related reporting changes. It helps keep report terminology consistent and reduces confusion for users reviewing GST return data.

Related: https://github.com/odoo/odoo/pull/179265

The login page now only shows the user switch option when there is more than one available user. This keeps the sign-in experience simpler for single-user cases while still supporting quick switching when multiple users are available.

If there is only one user in user switch, don't display it and propose the login form. If there is more than one user, display the user switch.

task-4160923

Studio exports no longer fail for databases that do not have the Website app installed. The export process now checks whether Website is available before looking for website-related data, preventing an unnecessary error for affected users.

**[FIX] web_studio: Fix export without website**
This commit fixes a bug where we would always check
for some website related fields and some records which
causes an error when website was not installed.

We now simply check that website is installed before
checking the fields.

This commit does not include a test as it would require
to uninstall the website addon and the testing framework
does not permit such a thing without introducing side
effects.

This update fixes an automated walkthrough used to verify the bank reconciliation interface. It helps keep accounting quality checks reliable, reducing the chance of unnoticed issues in future changes.

Resetting a report in Studio now also restores the header and footer layout configured on the company. This ensures reports return to the expected company branding when users choose to include the header and footer during a reset.

Set the external layout on the company. Edit a report that calls the "web.external_layout" template.

In the report editor, hit reset report and include the header/footer.

Before this commit, the company's layout was not reset.

After this commit it is resetted. The reason was that the external_layout is actually selecting the company's layout via a dynamic t-call, which is ignored by the code that retrieves views.

opw-4167257

The property field type selector now displays correctly inside its popover, instead of appearing with broken styling or behind other interface elements. This makes field configuration smoother and avoids confusion when users edit custom properties.

The dropdown inside the property field popover style was broken due to a dropdown refacor, some styles where not applied correctly and the field type dropdown was displayed behind the popover. (https://github.com/odoo/odoo/pull/137691).

This PR fixes the issue in 2 commits:
The first one adds a supplementary div around each overlay in the overlay container, this isolates each overlay so their z-index do not interfere, their order in the overlay-container is now sufficient to ensure a proper z-index, whatever the amount of popovers, modals, dropdowns, etc...

The second adapts the property field style and removes now unnecessary custom z-index values.

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

The spreadsheet document tests were adjusted to match improved keyboard behavior in the pivot rename side panel. This helps ensure the Enter and Escape key actions continue to work reliably for users when renaming pivot elements.

With PR[1], we have added handlers for 'Enter' and 'Escape' key events in the pivot rename sidepanel.

The test cases need to be updated accordingly.

[1] https://github.com/odoo/o-spreadsheet/pull/4793

Task: 4080323

Payroll accounting tests were reorganized so shared setup steps can be reused across country-specific payroll modules. Additional payslip validation checks were added for several localisations, helping reduce payroll calculation risks without changing day-to-day user workflows.

For tests in l10n_xx_payroll_account modules, we used the same util functions
 every time. These have now been moved to the hr_payroll_account module. This
 also adds a util function for setting up the usual employee, contract, etc.

 Task: 4040388

The demo kiosk setup has been moved from the IoT-specific self-order module into the main self-order module. This makes the sample kiosk experience available to more point-of-sale configurations, not only those using IoT.

We added a demo kiosk to the PoS in the `pos_self_order_iot` module, but now moved it to `pos_self_order` as it can benefit both.

Community PR: [https://github.com/odoo/odoo/pull/178080](https://github.com/odoo/odoo/pull/178080)

Before this commit: When a user with Billings rights scans a QR code using the vendor QR scan feature, an ir.act.window access error appears. After this commit: We fix the access error. And the QR scan feature works correctly as intended. Forward-Port-Of: odoo/enterprise#69700

Before this commit:
When a user with Billings rights scans a QR code using the vendor QR scan feature, an ir.act.window access error appears.

After this commit:
We fix the access error. And the QR scan feature
works correctly as intended.

Forward-Port-Of: odoo/enterprise#69700

The problem was that the button tag doesn't support drag & drop functionality in Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=568313). Steps to reproduce (On firefox): - Open Sign up - Open template - Try to drag and drop new compoent - You can only drag and drop through the text inside opw-4085496 Forward-Port-Of: odoo/enterprise#69691 Forward-Port-Of: odoo/enterprise#67772

The problem was that the button tag doesn't support drag & drop functionality in Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=568313).

Steps to reproduce (On firefox):

- Open Sign up

- Open template

- Try to drag and drop new compoent

- You can only drag and drop through the text inside

opw-4085496

Forward-Port-Of: odoo/enterprise#69691
Forward-Port-Of: odoo/enterprise#67772

### Steps to reproduce: - Create a second company COMP 2 - In the settings of COMP2 tick: Inter-Company Transactions Generate SO - With COMP1 create and confirm a PO for COMP2 for 1 unit of any product #### > Traceback ### Cause of the issue: These lines rely on stock models and hence provoque the traceback: https://github.com/odoo/enterprise/blob/d42af3270dea55acf247a99b815264ef96f0ac03/sale_purchase_inter_company_rules/models/purchase_order.py#L123-L132 They were added to transfe

### Steps to reproduce:

- Create a second company COMP 2
- In the settings of COMP2 tick: Inter-Company Transactions Generate SO
- With COMP1 create and confirm a PO for COMP2 for 1 unit of any product

#### > Traceback

### Cause of the issue:

These lines rely on stock models and hence provoque the traceback: https://github.com/odoo/enterprise/blob/d42af3270dea55acf247a99b815264ef96f0ac03/sale_purchase_inter_company_rules/models/purchase_order.py#L123-L132 They were added to transfer the `custom_product_template_attribute_value_id` during flows using stock routes. However, the stock dependency was removed from the `sale_purchase_inter_company_rules` module so that these lines should be moved to `sale_purchase_stock_inter_company_rules`

## opw-4151614

Forward-Port-Of: odoo/enterprise#69353

Note that the Swiss payroll modules haven't been translated into any other language than French so far, so that's why only the fr.po is fw-ported. Forward-Port-Of: odoo/enterprise#69654 Forward-Port-Of: odoo/enterprise#69630

Note that the Swiss payroll modules haven't been translated into any other language than French so far, so that's why only the fr.po is fw-ported.

Forward-Port-Of: odoo/enterprise#69654
Forward-Port-Of: odoo/enterprise#69630

We need TaxClosingNonPostedDependingMovesError inside account because it is now also used there to catch it when confirming batch of moves. Forward-Port-Of: odoo/enterprise#69518 Forward-Port-Of: odoo/enterprise#69206

We need TaxClosingNonPostedDependingMovesError inside account because it is now also used there to catch it when confirming batch of moves.

Forward-Port-Of: odoo/enterprise#69518
Forward-Port-Of: odoo/enterprise#69206

Description: - This accommodates scenarios where the main customer raises a ticket for a delivery partner. Changes: - Code modification for improved flexibility in handling cases where the main customer raises a ticket for the delivery partner. task-3623707 Forward-Port-Of: odoo/enterprise#69637 Forward-Port-Of: odoo/enterprise#52864

Description:
- This accommodates scenarios where the main customer raises a ticket for a delivery partner. 

Changes:
- Code modification for improved flexibility in handling cases where the main customer raises a 
ticket for the delivery partner.

task-3623707

Forward-Port-Of: odoo/enterprise#69637
Forward-Port-Of: odoo/enterprise#52864

Steps to reproduce ================== - Open studio - Edit any report - Make some changes - Click on discard - Click on cancel => UncaughtPromiseError Cause of the issue ================== When clicking on cancel, the promise is rejected https://github.com/odoo/odoo/blob/1ffcea337ba463c383483ca53ff57aa6b725b5a2/addons/web_editor/static/src/js/wysiwyg/wysiwyg.js#L1112 Solution ======== Instead of rejecting the promise, resolve it with the confirmation status opw-414

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

- Open studio
- Edit any report
- Make some changes
- Click on discard
- Click on cancel

=> UncaughtPromiseError

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

When clicking on cancel, the promise is rejected

https://github.com/odoo/odoo/blob/1ffcea337ba463c383483ca53ff57aa6b725b5a2/addons/web_editor/static/src/js/wysiwyg/wysiwyg.js#L1112

Solution
========

Instead of rejecting the promise, resolve it with the confirmation status

opw-4141192

Forward-Port-Of: odoo/enterprise#69646
Forward-Port-Of: odoo/enterprise#69127

Forward-Port-Of: odoo/enterprise#69591

Forward-Port-Of: odoo/enterprise#69591

The CAR (Código de Anotación de Registro) is an alphanumeric identifier composed of payment voucher data. It includes: - RUC number of the issuer: 11 numeric digits. - Type of payment voucher: 2 numeric digits. - Payment voucher series: 4 alphanumeric digits. - Payment voucher number: 10 alphanumeric digits.  Previously, support for SIRE reports was added. This change updates the general ledger t

The CAR (Código de Anotación de Registro) is an alphanumeric identifier composed of payment voucher data. It includes:
- RUC number of the issuer: 11 numeric digits.
- Type of payment voucher: 2 numeric digits.
- Payment voucher series: 4 alphanumeric digits.
- Payment voucher number: 10 alphanumeric digits.

![image](https://github.com/user-attachments/assets/d2a3e4c0-c9d0-4643-8596-c027d39f2599)


Previously, support for SIRE reports was added. This change updates the general ledger to ensure compatibility.

Adjusted the format of the 'book' field to include zero-padded and truncated document types, series, and folio numbers.

Legal reference: https://www.sunat.gob.pe/legislacion/superin/2021/anexo-112-2021.pdf

![image](https://github.com/user-attachments/assets/1d4e17a5-c593-4fbf-b99d-01d196650b5c)

Resolutions: [Resolución de Superintendencia N.° 112-2021](https://drive.google.com/file/d/19iWgqTeTn5WNIg3RpfAyHtF6xSIFL2rH/view?usp=sharing)

Forward-Port-Of: odoo/enterprise#68808
Forward-Port-Of: odoo/enterprise#67911

Steps to reproduce: [l10n_be] - Create a customer from Spain with the following VAT: A12345674 - Create an invoice with the customer - Go to EC Sales report Issue: The country code used in the report is "A1" Solution: Instead of inferring the country code from the VAT, we use the country code per se; to be a bit more defensive we fall back on the initial flow in case there is no country code. opw-4080828 Forward-Port-Of: odoo/enterprise#69125

Steps to reproduce:
[l10n_be]
- Create a customer from Spain with the following VAT: A12345674
- Create an invoice with the customer
- Go to EC Sales report

Issue:
The country code used in the report is "A1"

Solution:
Instead of inferring the country code from the VAT, we use the country code per se; to be a bit more defensive we fall back on the initial flow in case there is no country code.

opw-4080828

Forward-Port-Of: odoo/enterprise#69125

This PR fixes a wrong documentation link in the helpdesk team form view. Task-4102472 Forward-Port-Of: odoo/enterprise#68101

This PR fixes a wrong documentation link in the helpdesk team form view.

Task-4102472

Forward-Port-Of: odoo/enterprise#68101

Steps to reproduce: - Subscriptions > New > Set recurrence - Set 'Date of next invoice' in the future - Renew This should raise a ValidationError because renewing a subscription which was never started (no invoice) is invalid, as specified in the error message "You cannot upsell or renew a subscription that has not been invoiced yet". opw-4116538 Forward-Port-Of: odoo/enterprise#69361

Steps to reproduce:
- Subscriptions > New > Set recurrence
- Set 'Date of next invoice' in the future
- Renew

This should raise a ValidationError because renewing a subscription which was never started (no invoice) is invalid, as specified in the error message "You cannot upsell or renew a subscription that has not been invoiced yet".

opw-4116538

Forward-Port-Of: odoo/enterprise#69361

In this pr: https://github.com/odoo/odoo/pull/171795 we added some computed fields which caused an increase on the query count of the l10n_au_hr_payroll_account module, this commit will increase that. task: 4127269 Forward-Port-Of: odoo/enterprise#69704

In this pr: https://github.com/odoo/odoo/pull/171795 we added some computed fields which caused an increase on the query count of the l10n_au_hr_payroll_account module, this commit will increase that.

task: 4127269

Forward-Port-Of: odoo/enterprise#69704

Scanned barcodes were not saved (setting field in record do not register the change). Continue Production did not take advantage of saveModel parameter of doActionAndClose Forward-Port-Of: odoo/enterprise#69623 Forward-Port-Of: odoo/enterprise#69544

Scanned barcodes were not saved (setting field in record do not register the change).
Continue Production did not take advantage of saveModel parameter of doActionAndClose

Forward-Port-Of: odoo/enterprise#69623
Forward-Port-Of: odoo/enterprise#69544

This update removes an automatic copy action that was triggered immediately when using the Spreadsheet Share Button. Users will now have more control over when content is copied, improving the user experience by preventing unintended clipboard actions. This fix applies to both spreadsheet dashboards and document spreadsheets.

*spreadsheet* = spreadsheet_dashboard_edition documents_spreadsheet

opw-4144551