When a field service report is sent to a customer, the customer is now automatically added as a follower so they stay informed on related updates. The portal report view also shows amount due information and uses clearer field labels, improving customer visibility and communication.

before this commit, when report is send through 'send report' button. customer is not added to follower list.

This commit add customer to follower list when report is send through 'send report' button and add 'amount due' field  as well as rename some fields in portal

task: 3251754

This change adjusts Belgian payroll fleet behavior so that no fleet manager is assigned when none is available. This avoids showing or relying on an incorrect fallback person, making fleet-related payroll information cleaner and more accurate.

Remove the conditional statement on the user_id
to have nothing if there is no fleet manager.

linked to this PR in community https://github.com/odoo/odoo/pull/131576

task-3395095

The update reorganizes how mail-related records are stored internally so future maintenance and cleanup are easier. It also removes some unused discussion-service code, with no expected direct change for end users.

https://github.com/odoo/odoo/pull/133202

In preparation of code cleaning of models in store.
Entries in store are allocated per model, using the model name.
Records of a model can be accessed from `store[ModelName].records`.

Purpose: -------- This commit makes sure that the user icons in the options dropdown of an article (icons of "last edited by" and "created by") are aligned with the other icons of the dropdown. Task-3346593 Forward-Port-Of: odoo/enterprise#46157 Forward-Port-Of: odoo/enterprise#45471

Purpose:
--------
This commit makes sure that the user icons in the options dropdown of an article (icons of "last edited by" and "created by") are aligned with the other icons of the dropdown.

Task-3346593

Forward-Port-Of: odoo/enterprise#46157
Forward-Port-Of: odoo/enterprise#45471

Some layout issues such as the dropdown menu appearing behind the grid's contentn and content passing over the "Hours" column on horizontal scrolling have been fixed in this commit. follow up of task-3340318 Forward-Port-Of: odoo/enterprise#45864

Some layout issues such as the dropdown menu appearing behind the grid's contentn and content passing over the "Hours" column on horizontal scrolling have been fixed in this commit.

follow up of task-3340318

Forward-Port-Of: odoo/enterprise#45864

[FIX] account_reports: js options api Commit https://github.com/odoo/enterprise/commit/6c570325dc64adba441c748d834cee2c0fe488b7 removes the delete key from the _updateOption api. This commit restores it. Forward-Port-Of: odoo/enterprise#45985

[FIX] account_reports: js options api

Commit https://github.com/odoo/enterprise/commit/6c570325dc64adba441c748d834cee2c0fe488b7 removes the delete key from the _updateOption api.

This commit restores it.

Forward-Port-Of: odoo/enterprise#45985

Fixing: - l10n_hk_hr_payroll: fix out of contract error - l10n_be_hr_payroll: allow yearly advantages field to other countries Forward-Port-Of: odoo/enterprise#46271

Fixing:

- l10n_hk_hr_payroll: fix out of contract error 
- l10n_be_hr_payroll: allow yearly advantages field to other countries

Forward-Port-Of: odoo/enterprise#46271

At the moment, the way in which the SAF-T template populates partner contacts in the XML's Contact->ContactPerson nodes makes no sense at all. The current behaviour is that for each partner, we create a ContactPerson node for itself and for each of its children. That means that if you have n contacts at a partner company, you will end up with n+1 ContactPerson nodes (one for the company, and one for each of its employees). Similarly, if your own company has n employees, you will have n+1 C

At the moment, the way in which the SAF-T template populates partner contacts in the XML's Contact->ContactPerson nodes makes no sense at all. The current behaviour is that for each partner, we create a ContactPerson node for itself and for each of its children.

That means that if you have n contacts at a partner company, you will end up with n+1 ContactPerson nodes (one for the company, and one for each of its employees).

Similarly, if your own company has n employees, you will have n+1 ContactPerson nodes in the SAF-T header, one for your company and one for each of your employees.

This behaviour is absurd for several reasons.
- First of all, the government has no use for more than one contact person at your company and at your partner companies. So why list them all?
- ~~Secondly, publishing the names of all your employees in your SAF-T export is potentially a big leak of sensitive information.~~ (not an issue because by default employees are not contacts of the Company.)
- Thirdly, if the partner is a company, it makes no sense to put it as its own ContactPerson. ContactPersons must be natural persons.
- Fourthly, the ContactPerson node is optional in the SAF-T spec (except when you need to provide a ContactPerson for your own company in the SAF-T header). So, when we don't have a contact person for a particular partner, we should just leave that node blank.

This commit tries to handles this all in a more sensible way:
- If the partner is your own company, put all child contacts of the company as ContactPersons.
- If the partner is an individual, put him/her as their own ContactPerson.
- If the partner is a company, find the active child partner that has the lowest ID (generally a good guess for the main PoC at that partner) and put them as the ContactPerson for the company.

SAF-T spec: https://www.oecd.org/tax/administration/45167181.pdf

taskid: 3395016

Forward-Port-Of: odoo/enterprise#46115
Forward-Port-Of: odoo/enterprise#42743

Previously if an IoT box had connection issues, it would throw an unhandeled error when trying to access it. This commit adds a condition to check if the device is properly connected before accessing it. Forward-Port-Of: odoo/enterprise#46294 Forward-Port-Of: odoo/enterprise#46188

Previously if an IoT box had connection issues, it would throw an unhandeled error when trying to access it. This commit adds a condition to check if the device is properly connected before accessing it.

Forward-Port-Of: odoo/enterprise#46294
Forward-Port-Of: odoo/enterprise#46188