The time off dashboard search has been simplified so employees only see their own dashboard information. This reduces confusion by removing employee-based filtering where it is not needed for the user’s personal view.

remove employee in search bar; only you will see your own dashboard.

task : 3679662

The analytic account form layout has been adjusted so budget information appears after the account property fields. This creates a more consistent and logical order for users reviewing or editing analytic account details.

This PR involves updating the xpath selector for the patch that adds the budget notebook to the analytic account view. The revised selector ensures that the budget notebook is inserted at the end of the view form sheet. This modification guarantees that the property fields, as defined in the parent view, will precede the placement of the budget notebook.

task-3594814

The Knowledge app's automated checks for article history were updated to match recent interface changes. This helps keep quality checks reliable without changing the user-facing feature itself.

This commit is the enterprise counterpart of commit [1]. Since we now use the Notebook component in the HistoryDialog, the classes have changed, and the tour testing the history feature needed to be adapted.

Now, the tour is correctly using the latest selectors.

[1]: f301d61bf8a751fabacd6f6d4541bcd0489c48ab

Linked Community PR: https://github.com/odoo/odoo/pull/153372

Steps to reproduce: - Go to Helpdesk - Navigate to Configuration > Teams - Turn off the 'sla policies' from the form view of all teams. - Check in the reporting section the 'sla status analysis' menu item is visible for the teams. Issue: - The 'sla status analysis' menu item shouldn't be visible if the 'sla policies' feature is disabled on all teams Solution: - Updated the visibility of the 'sla status analysis' menu item based on the 'sla policies' by adding the groups task

Steps to reproduce:

- Go to Helpdesk
- Navigate to Configuration > Teams
- Turn off the 'sla policies' from the form view of all teams.
- Check in the reporting section the 'sla status analysis' menu item is visible for the teams.

Issue:

- The 'sla status analysis' menu item shouldn't be visible if the 'sla policies' feature is disabled on all teams

Solution:

- Updated the visibility of the 'sla status analysis' menu item based on the 'sla policies' by adding the groups

task-3549328

Forward-Port-Of: odoo/enterprise#50099

### [IMP] l10n_mx_edi: duplicate check using fiscal folio As every fiscal folio on a vendor bill in Mexico is unique, we can easily check that to find duplicates. This change extends the default duplicate vendor bill check to first see if it can find duplicates with the same folio fiscal. If it doesn't find any, it will apply the generic duplicate check. task-3590442 ### [IMP] l10n_mx_edi: import withholding taxes Currently when importing a Mexican vendor bill, we skip the withhol

### [IMP] l10n_mx_edi: duplicate check using fiscal folio

As every fiscal folio on a vendor bill in Mexico is unique, we can easily check that to find duplicates.

This change extends the default duplicate vendor bill check to first see if it can find duplicates with the same folio fiscal. If it doesn't find any, it will apply the generic duplicate check.

task-3590442

### [IMP] l10n_mx_edi: import withholding taxes

Currently when importing a Mexican vendor bill, we skip the withholding taxes defined on the lines.

In this change, we also allow importing the withholding taxes when we find at least one that matches in the database.

task-3590442

### [IMP] l10n_mx_edi: flag "to check" on issues with import

When we're importing a Mexican vendor bill and we're unsure about something, like a tax that couldn't be found or multiple possible taxes, a message is logged in the chatter of that invoice in Odoo. However, it is not easy to identify which imported bills have errors later on when we have a bunch of them.

In order to make that easier, we flag the vendor bill as "to check" whenever we encounter an uncertainty at import, so the user can easily filter on that to follow up on these invoices.

task-3590442

Forward-Port-Of: odoo/enterprise#56064
Forward-Port-Of: odoo/enterprise#53128

runbot ticket: 56443 Forward-Port-Of: odoo/enterprise#55791 Forward-Port-Of: odoo/enterprise#55406

runbot ticket: 56443

Forward-Port-Of: odoo/enterprise#55791
Forward-Port-Of: odoo/enterprise#55406

### **Version:** - 17.0 ### **Cause:** When a subscription is not paid automatically, We sent an email to customers to inform them that we would be retrying. ### **Improvement:** In this commit, a button has been added to the email that enables users to pay for failed subscription payments directly. task-3640650 ---- I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr) Forward-Port-Of: odoo/enterprise#55379 F

### **Version:**

- 17.0

### **Cause:**
When a subscription is not paid automatically,
We sent an email to customers to inform them that we would be retrying.

### **Improvement:**
In this commit, a button has been added to the email that enables users to
pay for failed subscription payments directly.


task-3640650

----
I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr)

Forward-Port-Of: odoo/enterprise#55379
Forward-Port-Of: odoo/enterprise#53046

`_build_query` is a rat's nest of randomly sprinkled `SQL`, which seems to end in the sql injection checker getting confused and non-deterministic. Do some cleaning to try and make it more understandable for the linter. Forward-Port-Of: odoo/enterprise#56367

`_build_query` is a rat's nest of randomly sprinkled `SQL`, which seems to end in the sql injection checker getting confused and non-deterministic.

Do some cleaning to try and make it more understandable for the linter.

Forward-Port-Of: odoo/enterprise#56367