A test tour in Website Studio was made more precise so it waits for the right page update before continuing. This reduces false failures in automated checks and helps keep releases stable without changing user-facing behavior.

in tour engine, we listen for mutations in the DOM in order to look for the element pointed to by the "trigger". If it is found, we execute run().
In this tour, the div[name='name_slugified'] element is found even before the textContent modifications have been made. To resolve the problem, simply be more precise in the trigger selector. It should be noted that we can therefore remove the first assertion in run() which amounts to doing exactly the same thing as the trigger.

This update restores the date filter behavior in the Mexican closing reports after a broader reporting change left this module out. Users working with these reports should now see date filtering work consistently with the rest of the accounting reports.

The commit 6fe06c57fa7d4bce9ad9a9df0f773678047b9d06 changed the way the date filter works in the account reports. During the change, it forgot to apply the change to this niche localisation module.

This update corrects several internal filters and default values across multiple Odoo apps so they no longer require unnecessary processing. It should make these screens and automated rules behave more consistently without changing day-to-day workflows.

…invoices Steps to Reproduce on Runbot: 1. Set up AvaTax in Accounting settings 2. Make sure that the “Use AvaTax API” field is checked for the fiscal position named “Automatic Tax Mapping (AvaTax)” 3. Go to “Tax Groups” and for the record called “Tax 15%”, add “Test” to the field called “Preceding Subtotal” 4. Go to the Product Category called “All” and choose any selection for the field called “AvaTax Category” 5. Make an invoice and add the fiscal position named “Automatic Tax Mappi

…invoices

Steps to Reproduce on Runbot:

1. Set up AvaTax in Accounting settings
2. Make sure that the “Use AvaTax API” field is checked for the fiscal position named “Automatic Tax Mapping (AvaTax)”
3. Go to “Tax Groups” and for the record called “Tax 15%”, add “Test” to the field called “Preceding Subtotal”
4. Go to the Product Category called “All” and choose any selection for the field called “AvaTax Category”
5. Make an invoice and add the fiscal position named “Automatic Tax Mapping (AvaTax)”
6. Save then print the invoice. Notice on the printed invoice that above the box called “Total”, the box called “Untaxed Amount” shows up with no tax box.
7. Uncheck the “Use AvaTax API” field for the fiscal position named “Automatic Tax Mapping (AvaTax)” (This step is basically the inverse of step 2)
8. Print the invoice again and notice this time that the box will instead be called “Test” (which we set in step 3) and that a box showing the tax amount will show up.

This commit fixes the issue so that the value in "Preceding subtotal" is shown for printed Avatax invoices too.

opw-4027280

Forward-Port-Of: odoo/enterprise#66932

When `industry_fsm` is installed, the form of `project.project` contains a section `Field Service` with only one setting (`is_fsm`). This option is only visible in only visible in debug mode, so the whole section should be displayed only under this conditon. => The group `base.group_no_one` has been added to the section. When `industry_fsm_report` is installed, another setting appears under that section (`worksheet_template_id`), so the section should be displayed. => The group that is adde

When `industry_fsm` is installed, the form of `project.project` contains a section `Field Service` with only one setting (`is_fsm`). This option is only visible in only visible in debug mode, so the whole section should be displayed only under this conditon. => The group `base.group_no_one` has been added to the section.

When `industry_fsm_report` is installed, another setting appears under that section (`worksheet_template_id`),
so the section should be displayed.
=> The group that is added in `industry_fsm` is removed then.

task-3916982

Forward-Port-Of: odoo/enterprise#62270

How to reproduce (on 17.0 onwards): - Helpdesk -> new ticket form - set the name of the ticket (do not save the record) - then, set a partner to a existing partner - The display_name on the top displays 'name - #False' Expeceted behavior: - instead of displaying 'name - #False', it should display 'name' if the ticket_ref is not defined yet. After this commit, the display_name only displays the ticket_ref (#ID) if it exists. Test have been added for this purpose. Task: 3893076 Forw

How to reproduce (on 17.0 onwards):
- Helpdesk -> new ticket form
- set the name of the ticket (do not save the record)
- then, set a partner to a existing partner
- The display_name on the top displays 'name - #False'

Expeceted behavior:
- instead of displaying 'name - #False', it should display 'name' if the ticket_ref is not defined yet.

After this commit, the display_name only displays the ticket_ref (#ID) if it exists. Test have been added for this purpose.

Task: 3893076

Forward-Port-Of: odoo/enterprise#66471

Problem --- When a stock picking is clicked from the barcode view, its responsible is always automatically assigned to the current user. Fix --- assign current user only if they change anything (validate, edit a line, etc) but not if they just look. opw-3878484 Forward-Port-Of: odoo/enterprise#66897 Forward-Port-Of: odoo/enterprise#61456

Problem
---
When a stock picking is clicked from the barcode view,
its responsible is always automatically assigned to the current user.

Fix
---
assign current user only if they change anything (validate, edit a line,
etc) but not if they just look.

opw-3878484

Forward-Port-Of: odoo/enterprise#66897
Forward-Port-Of: odoo/enterprise#61456

To reproduce: Create a branch for your company On this branch, create an overdue invoice for a partner. Change company for the parent company. Go to Follow-up Reports Go on this partner. You see the invoice appearing in the list Click on Follow-up and print => The pdf does not contain the invoice from the branch The issue is that we check on company and not on the company and branches. opw-3988003 Forward-Port-Of: odoo/enterprise#66896

To reproduce:
Create a branch for your company
On this branch, create an overdue invoice for a partner. 
Change company for the parent company.
Go to Follow-up Reports
Go on this partner.
You see the invoice appearing in the list
Click on Follow-up and print
=> The pdf does not contain the invoice from the branch

The issue is that we check on company and not on the company and branches.

opw-3988003

Forward-Port-Of: odoo/enterprise#66896

With task-3336242, the control panel's dropdown button's display condition was changed from <= xl display to <= md display. Hence, this PR changes the display condition of buttons in the planning gantt view to align with this new behavior. The bootstrap classes that were used to attain this effect are now removed, replaced by a t-if="env.isSmall". This allows us to have only one of the two implementation present in the dom, and to change the display condition to <= md. task-4005521 Forwar

With task-3336242, the control panel's dropdown button's display condition was changed from <= xl display to <= md display. Hence, this PR changes the display condition of buttons in the planning gantt view to align with this new behavior.

The bootstrap classes that were used to attain this effect are now removed, replaced by a t-if="env.isSmall". This allows us to have only one of the two implementation present in the dom, and to change the display condition to <= md.

task-4005521

Forward-Port-Of: odoo/enterprise#65301

The settle due accounts was not always shown on the partner screen. Now it's always shown, and when the user doesn't have any amount due the text changes to "Deposit Money" instead of "Settle Due Accounts" Steps to reproduce: ------------------- * Install pos_settle_due module * Open PoS session * Open partner list * Click on details for any partner with no due > Observation: The "Settle Due Accounts" button is missing Why the fix: ------------ We always show the button, but change

The settle due accounts was not always shown on the partner screen. Now it's always shown, and when the user doesn't have any amount due the text changes to "Deposit Money" instead of "Settle Due Accounts"

Steps to reproduce:
-------------------
* Install pos_settle_due module
* Open PoS session
* Open partner list
* Click on details for any partner with no due
> Observation: The "Settle Due Accounts" button is missing

Why the fix:
------------
We always show the button, but change the text to better match the behavior. If there is no amount due the text says "Deposit Money" and when the user has some amount due it says "Settle Due Accounts"

opw-3925397

Forward-Port-Of: odoo/enterprise#66768
Forward-Port-Of: odoo/enterprise#65762

Community: https://github.com/odoo/odoo/pull/173324 Design Themes: https://github.com/odoo/design-themes/pull/831 Forward-Port-Of: odoo/enterprise#66743

Community: https://github.com/odoo/odoo/pull/173324
Design Themes: https://github.com/odoo/design-themes/pull/831

Forward-Port-Of: odoo/enterprise#66743

Context: On an upgraded database we detected that the resource calendar inherited views where disabled, because they were not able to find parent element. The full timeline is as below: - 2021-01-01: commit odoo/enterprise@1d9fdd624497 introduced `hr_payroll.resource_calendar_view_tree` view - 2021-02-05: commit odoo/enterprise@0506d4e6fa18 introduced `hr_contract.resource_calendar_view_tree` view (with `contracts_count` field) - 2024-07-02: commit odoo/enterprise@1f03fb675922 updated

Context:

On an upgraded database we detected that the resource calendar inherited views where disabled, because they were not able to find parent element.

The full timeline is as below:

- 2021-01-01: commit odoo/enterprise@1d9fdd624497 introduced `hr_payroll.resource_calendar_view_tree` view
- 2021-02-05: commit odoo/enterprise@0506d4e6fa18 introduced `hr_contract.resource_calendar_view_tree` view (with `contracts_count` field)
- 2024-07-02: commit odoo/enterprise@1f03fb675922 updated `hr_payroll.resource_calendar_view_tree` view to add a field after `contracts_count` field.

For databases that were update with each individual changes (at specified date), the `hr_payroll` inherited view will have a lower id than the `hr_contract` one and as such will be applied before (considering the standard view order).

  And following commit odoo/enterprise@1f03fb675922 this will raise a ValidationErorr:

`Element '<field name="contracts_count">' cannot be located in parent view`

This commit update `hr_payroll.resource_calendar_view_tree` view to inherit from the view that really add the `contracts_count` field.

Forward-Port-Of: odoo/enterprise#66913

Steps to Reproduce: ----------- Install the helpdesk_account and helpdesk_sale_timesheet module. Go to the ticket form view. Perform a refund or reverse action. Click on the 'Credit Notes' stat button. Observe that the list view of credit notes is empty. Cause: ---------- When the helpdesk_sale_timesheet module is installed, the action_view_invoices method gets overridden. Fix: --------- We have renamed the actions in the helpdesk_account module to avoid conflicts

Steps to Reproduce:
-----------

  Install the helpdesk_account and helpdesk_sale_timesheet module.
  Go to the ticket form view.
  Perform a refund or reverse action.
  Click on the 'Credit Notes' stat button.
  Observe that the list view of credit notes is empty.

Cause:
----------
  When the helpdesk_sale_timesheet module is installed, the action_view_invoices method gets overridden.

Fix:
---------
  We have renamed the actions in the helpdesk_account module to avoid conflicts.

task-3972344

Forward-Port-Of: odoo/enterprise#65859

Steps to reproduce: - Open planning app - Create a shift for user who has leave during the slot. - You will get an warning in the form view. Issue: - Warning is not aligned vertically Cause; - This is not issue of alignment but due to a empty div created for conflict slot warning. Solution: - A constraint to stop the empty div which causes alignment issues task-3888018 Forward-Port-Of: odoo/enterprise#62645

Steps to reproduce:

- Open planning app
- Create a shift for user who has leave during the slot.
- You will get an warning in the form view.

Issue:

- Warning is not aligned vertically

Cause;

- This is not issue of alignment but due to a empty div created for conflict slot warning.

Solution:

- A constraint to stop the empty div which causes alignment issues

task-3888018

Forward-Port-Of: odoo/enterprise#62645

Before this commit, in about 8% of the time for some test tours, some edition of the report was triggered before the OdooEditor had a chance to start, so the concerned step failed. After this commit, there is no such race condition, as we add OdooEditor's specific class to the step selectors. runbot-error-29949 (and all linked error) Forward-Port-Of: odoo/enterprise#66886 Forward-Port-Of: odoo/enterprise#66815

Before this commit, in about 8% of the time for some test tours, some edition of the report was triggered before the OdooEditor had a chance to start, so the concerned step failed.

After this commit, there is no such race condition, as we add OdooEditor's specific class to the step selectors.

runbot-error-29949 (and all linked error)

Forward-Port-Of: odoo/enterprise#66886
Forward-Port-Of: odoo/enterprise#66815

This commit adds the missing neutralization necessary for the l10n_fr_reports module introduced in 06f32096749a8df29b248f29698226cf996e9106 The purpose of the standard neutralization framework is to allow us to create database copies that will not interact with external systems in ways that could impact the production database (or if it is not possible to prevent the interactions, make sure that they are benign or won't result in actual changes), or impact the customers of the operator of th

This commit adds the missing neutralization necessary for the l10n_fr_reports module introduced in
06f32096749a8df29b248f29698226cf996e9106

The purpose of the standard neutralization framework is to allow us to create database copies that will not interact with external systems in ways that could impact the production database (or if it is not possible to prevent the interactions, make sure that they are benign or won't result in actual changes), or impact the customers of the operator of the production database.

This is mainly useful to allow safe support investigation on database duplicates.

opw-3928199

Forward-Port-Of: odoo/enterprise#66838