When users open Documents from a partner record, the document request form now automatically fills the 'Request to' field with that partner. This saves time and reduces manual entry when requesting documents from customers, vendors, or other contacts.

When reaching Documents from the Documents stat button of a partner, prefill the 'Request to' field with the partner when clicking on Request as there are many chances that we'll ask this partner for a document.

task-3688422

A new automated test was added to confirm that Field Service task grouping by assigned user continues to work after shared logic was introduced with Project. This helps reduce the risk of regressions in planning and task management views without changing day-to-day user behavior.

The user_id group expand implementation was changed recently in order for the field service and the project apps to share implementations.

There is a test for the project's functionality but no tests for the field service functionality and thus a new test was added for it.

task-3696707

Belgian payroll users now get a clear warning when trying to update working schedules for multiple contracts at once. This avoids a system error and helps users complete the task correctly by updating one contract at a time.

Updating working schedules in batch mode for contracts currently causes a system error. This commit ensures that the update process now raises a user error if multiple contracts are selected.

Task-3571866

Intrastat country and region settings have been moved to the shared Intrastat module so they can support more country localizations beyond Belgium. This keeps configuration consistent and hides region settings when they do not apply to a company's country.

… higher model

The fields company_country_id and intrastat_region_id were both defined in l10n_be_intrastat. These fields are now required on other localizations, such as France which will come in a later commit. For this reason, these fields need to be defined on account_intrastat to be used by all possible localization.

The view of the intrastat region (visible in the settings) must also be defined in account_intrastat, and make the field invisible if the company country has no intrastat region defined.

task-3691571

This update renames the French localization accounting module to better reflect its purpose and align related dependencies. It mainly affects internal module organization, helping maintain consistency without changing day-to-day business functionality.

This update reorganizes how spreadsheet pivot tables are prepared and named, reducing internal complexity ahead of broader pivot table capabilities. Business users should see little immediate change, but the work helps make future spreadsheet pivot improvements easier and more reliable.

Before this PR, the user will receive a traceback whenever they try to open locked documents. Technical Reason: In this commit, https://github.com/odoo/enterprise/commit/ae6604318bfbea4c389808b51d0cbf2546dc7373 user service is removed and replaced by a simple user object. After this PR, the user can easily open locked documents without any traceback. **Task**-3720837 Forward-Port-Of: odoo/enterprise#55937

Before this PR, the user will receive a traceback whenever they try to open locked documents.

Technical Reason:
In this commit, https://github.com/odoo/enterprise/commit/ae6604318bfbea4c389808b51d0cbf2546dc7373 user service is removed and replaced by a simple user object.

After this PR, the user can easily open locked documents without any traceback.

**Task**-3720837

Forward-Port-Of: odoo/enterprise#55937

It appears that some user need to have the german translation on the dutch localisation. This commit will translate the following files: - Balance sheet - Profit and loss task: 3682464 Forward-Port-Of: odoo/enterprise#56189 Forward-Port-Of: odoo/enterprise#55207

It appears that some user need to have the german translation on the dutch localisation. This commit will translate the following files:
- Balance sheet
- Profit and loss

task: 3682464

Forward-Port-Of: odoo/enterprise#56189
Forward-Port-Of: odoo/enterprise#55207

Purpose ======= Fix the trash button which was disappearing from the inspector when multiple documents are selected. Specifications ============== When only one document is selected, the trash button is displayed next to the "Name" field in the inspector. When multiple documents are selected, this "Name" field is hidden preventing the trash button to be displayed. Moving the trash button next to the "Contact" field when multiple documents are selected for it to keep being accessible.

Purpose
=======
Fix the trash button which was disappearing from
the inspector when multiple documents are selected.

Specifications
==============
When only one document is selected, the trash button is displayed next to the "Name" field in the inspector. When multiple documents are selected, this "Name" field is hidden preventing the trash button to be displayed. Moving the trash button next to the "Contact" field when multiple documents are selected for it to keep being accessible.

Task-3700965

Forward-Port-Of: odoo/enterprise#55041

When increasing an asset with constant periods, we get an error on increase asset validation, due to the asset lifetime days being wrongly computed. Steps: - Asset configuration: - Original value: 1200 - Acquisition date: 10/01/2023 - Method: linear - Duration: 12 Months - Computaion: Constant Periods - Confirm asset - Modify it: action 'modify' and date 01/15/2024 - Validate -> UserError("The remaining value on the last depreciation line must be 0") This is due to the fact that the fiel

When increasing an asset with constant periods, we get an error
on increase asset validation, due to the asset lifetime days
being wrongly computed.

Steps:

- Asset configuration:
	- Original value: 1200
	- Acquisition date: 10/01/2023
	- Method: linear
	- Duration: 12 Months
	- Computaion: Constant Periods
- Confirm asset
- Modify it: action 'modify' and date 01/15/2024
- Validate
-> UserError("The remaining value on the last depreciation line must be
0")

This is due to the fact that the field `asset_lifetime_days` is an
Integer field and it is computed to satisfy this constraint.
With this commit we change this field (non stored) from Integer
to Float and adapt its computation.

opw-3691191

Forward-Port-Of: odoo/enterprise#55648

Create an invoice for a customer who lives in the UE but his/her VAT number has not been verified by the VIES system, so the transaction with this partner should be considered with fiscal position 'Regimen Nacional' because the IVA should appear as a domestic customer. When creating the invoice with fiscal position 'Regimen Nacional', ensure field for tax report 349 is empty in the tab 'AEAT data' as well as tax in the invoice exists. Open Tax Report 349 Issue: There will be values for thes

Create an invoice for a customer who lives in the UE but his/her VAT number has not been verified by the VIES system, so the transaction with this partner should be considered with fiscal position 'Regimen Nacional' because the IVA should appear as a domestic customer.
When creating the invoice with fiscal position 'Regimen Nacional', ensure field for tax report 349 is empty in the tab 'AEAT data' as well as tax in the invoice exists.
Open Tax Report 349

Issue: There will be values for these 2 lines which should not be there, as this specific invoice should not appear in tax report 349

opw-3673456

Forward-Port-Of: odoo/enterprise#56103
Forward-Port-Of: odoo/enterprise#55504

It is possible that two expressions (possibly of different report, linked together by a cross_report expression) needing to be evaluated at the same time share the same tax tags formula. When this case happens, the result of the engine function should be in the form {(formula, recordset_of_expr_1_and_2): result} (assuming there is no other expression to evaluate, for the sake of simplicity). Before this fix, in this situation, the engine instead returned: { (formula, expr_1): result,

It is possible that two expressions (possibly of different report, linked together by a cross_report expression) needing to be evaluated at the same time share the same tax tags formula. When this case happens, the result of the engine function should be in the form {(formula, recordset_of_expr_1_and_2): result} (assuming there is no other expression to evaluate, for the sake of simplicity).

Before this fix, in this situation, the engine instead returned: {
    (formula, expr_1): result,
    (formula, expr_2): result,
    (formula, recordset_of_expr_1_and_2): empty_value,
}

Because of that, the report ended up evalutating these expressions with an empty result. This was spotted when forward-porting https://github.com/odoo/enterprise/commit/c8beb3559b9199fc2f72773dd5dedf871cf2406b , since the new error it introduces raised in such case, since the value initially computed for expr_1/expr_2 got overwritten.

This was wrong, and was due to the fact the result dict was first initialized using the full key of the formulas_dict (hence grouping expr_1 and expr_2 into a common recordset), and then wrongly iterated on all the expressions contained in the keys. We fix that by using the full key everywhere.

Forward-Port-Of: odoo/enterprise#56162

Fix the activity view inspector which was always displaying 0 Documents and 0 MB. The number of documents and the file size is now correctly updated. Getting the file size with the DocumentsDataPointMixin mixin. Task-3700259 Forward-Port-Of: odoo/enterprise#56139 Forward-Port-Of: odoo/enterprise#55011

Fix the activity view inspector which was always displaying 0 Documents and 0 MB.
The number of documents and the file size is now correctly updated.
Getting the file size with the DocumentsDataPointMixin mixin.

Task-3700259

Forward-Port-Of: odoo/enterprise#56139
Forward-Port-Of: odoo/enterprise#55011

Avoid affect document type assignation for no Peruvian countries Forward-Port-Of: odoo/enterprise#56100

Avoid affect document type assignation for no Peruvian countries

Forward-Port-Of: odoo/enterprise#56100

Summary: When we unfold an account and show journal entries in the general ledger (with the "Hierarchy and Subtotals" option checked), the journal entries do not appear on the XLSX report. Steps to reproduce: 1. Enable debug mode 2. Create a new account group (Accounting > Configuration > Accounting > Account Groups) with a code prefix from 1 to 9 3. Open the general ledger (Accounting > Reporting > Audit Reports > General Ledger) and check the option "Hierarchy and Subtotals" 4. Unf

Summary:
When we unfold an account and show journal entries in the general ledger (with the "Hierarchy and Subtotals" option checked), the journal entries do not appear on the XLSX report.

Steps to reproduce:
	1. Enable debug mode
	2. Create a new account group (Accounting > Configuration > Accounting > Account Groups) with a code prefix from 1 to 9
	3. Open the general ledger (Accounting > Reporting > Audit Reports > General Ledger) and check the option "Hierarchy and Subtotals"
	4. Unfold a line until you can see journal entries (e.g., "101000 Current Assets" on runbot)
	5. Export the general ledger in XLSX, and open it: the journal entries do not appear

Cause:
In the local stack, there is a field "unfolded_lines" that is a list containing the unfolded lines in absolute format (e.g., if account A is in account group G, the line is noted as "G|A").
However, when checking if an account is unfolded, it checks if the name of the account is in this field (just the name and not the group/account), which is not the case if the account is in an account group. In this case, the children are not displayed because only the content of the unfolded lines is shown.

Fix:
Modify the check for whether an account is unfolded: check if the name in absolute format is in the unfolded_lines list.


opw-3649550

Forward-Port-Of: odoo/enterprise#55753
Forward-Port-Of: odoo/enterprise#54385

Before this commit, the US localisation was adding charts of account to rules only for the demo US company. However, the base company is based in San Francisco and should also have its demo data updated. task-3713709 Forward-Port-Of: odoo/enterprise#55524

Before this commit, the US localisation was adding charts of account to rules only for the demo US company. However, the base company is based in San Francisco and should also have its demo data updated.

task-3713709

Forward-Port-Of: odoo/enterprise#55524

We revert the below commit in this commit due to some issues that arose, so we decided to remove the default Indian public holiday. commit-https://github.com/odoo/enterprise/commit/403c8faf24afe79a533bab19d6c994ed5b5edc3a task-3693329 Forward-Port-Of: odoo/enterprise#56119

We revert the below commit in this commit due to some issues
  that arose, so we decided to remove the default Indian public holiday.

 commit-https://github.com/odoo/enterprise/commit/403c8faf24afe79a533bab19d6c994ed5b5edc3a

task-3693329

Forward-Port-Of: odoo/enterprise#56119

This update corrects a technical error in the Sendcloud delivery integration's filter widget that was using an invalid type comparison. The fix ensures the widget functions properly when filtering delivery options, improving the reliability of the shipping selection process for users.

This update corrects the label for tax unit fields in the Indian GST reporting module from "VAT Units" to "GST Units" to accurately reflect India's Goods and Services Tax system. This ensures the system uses correct terminology that aligns with Indian tax regulations and improves clarity for users working with GST returns.

Before this PR:
The string for the `tax_unit_id` field was 'VAT Units'.

After this PR:
The `tax_unit_id` field's string has been renamed 'GST Units'.

Task-3726861

Forward-Port-Of: odoo/enterprise#56120

This update corrects the visual layout of new projects by reducing the excessive gap between the email alias and project title. When creating a new project with email functionality enabled, the spacing was unnecessarily large, making the interface look awkward. The fix adjusts the spacing to provide a cleaner, more professional appearance.

Steps:
--------
- Install project.
- Go to settings and select Custom Email Servers.
- Add alias domain.
- Then go to the project.
- Create a new project.
- The gap between the email alias and project title is too much.

Issue:
--------
-When we create a new project the gap between the email alias and project name is too
 much when only the project is installed and there are no options to display. 

Cause:
----------
-The margin-top taking too much space.

Fix:
-----
-After this commit the space between email-alias and project name is decreased.

task-3550638

Forward-Port-Of: odoo/odoo#153091
Forward-Port-Of: odoo/odoo#139908

This update fixes a visual alignment issue with table column menus when using right-to-left (RTL) language modes. The table menu now displays correctly positioned in RTL mode, improving the user experience for customers using RTL languages.

**Description of the issue this PR addresses:**

Previously, In RTL mode, the table columns menu were misaligned, causing a visual discrepancy in the UI.Now, Implemented a fix to correctly position the table menu columns in RTL mode, ensuring proper alignment and resolving the visual misalignment issue.

task-[3695715](https://www.odoo.com/web#id=3695715&cids=2&menu_id=6478&action=4043&model=project.task&view_type=form)

Forward-Port-Of: odoo/odoo#151955