Helpdesk forum pages now point users to the updated forum profile location. This keeps profile access working as the forum experience expands to support browsing and searching across all forums.

The route model to the user forum profile has been modified as part of a new feature that makes possible for users to have an overview and search in all forums.

The link in the template(s) must be modified accordingly.

see odoo/odoo#129123
task-2676848

SAF-T report handling has been reorganized so it now sits with the General Ledger reporting flow instead of the broader accounting report area. This makes the reporting setup cleaner and easier to maintain across country-specific SAF-T implementations, without changing the intended business output.

- Currently, all SAF-T related code is still located in 'account.report'.
- That does not make much sense since it applies to the General Ledger which has its own custom handler
- The goal of this task is to move all SAF-T related code from 'account.report' to 'account.general.ledger.report.handler'

task-id: 3423844

Users can now adjust the displayed currency symbol without enabling debug mode, helping make documents clearer when different currencies share the same symbol. The eBay currency setting was repositioned in the currency form to make room for this clearer display option.

Description of the issue/feature this PR addresses:

Prior to this, when multiple currencies with the same symbol where to appear in a same document or be sent from a country to another with the same currency symbol, the only information the recipient had was the currency symbol leading to lack of clarity.

Desired behavior after PR is merged:

This set of two PR has for objective to give the user the possibility to edit the symbol curency that is displayed everywhere so that if he feels like the documents and views are lacking clarity, he can improve it.

This was already an option before but only when the debug mode was active.

This commit has the purpose moving the "Use on eBay" option in the currency form view so that the displayed symbol can be added to the right column.

Adding this, the "Use on eBay" option is moved to the left column.

task-3484335

Community PR : https://github.com/odoo/odoo/pull/133554

Users can now search follow-up reports by customer or report name and by the responsible person. This makes it faster for teams to find the right follow-up information and manage outstanding items more efficiently.

Add a search filter on the followup reports view: on the 'name' (`name`) and on the 'responsible' (`followup_responsible_id`).

task-3460484

Warehouse barcode users are now prompted to confirm a location when scanning a reserved product from somewhere other than its expected source. This helps prevent picking mistakes when workers forget to scan the new shelf or location between products.

When a product is scanned and this product is reserved in another location than the current one, the application will ask the user to confirm they want to take this product in the current location by scanning the source's barcode.

The purpose of this commit is to avoid scan error by taking a product in the wrong location because user could forget to scan the location between two different products. Imagine the following case:
- There is a delivery for Product A (reserved in Shelf 1) and Product B (reserved in Shelf 2);
- First, the user scans Shelf 1, than scans Product A. So far so good;
- Now the user scans Product B. The question is: do they want to take Product B from Shelf 1, or did they forget to scan Shelf 2 first ?

This issue is relevant only when the products are reserved and the scan of the source location is mandatory.

To handle this case, a product reserved in a location can be taken from another location only if this other location was scanned just before the product. A notification informs the user they have to scan the location.
So, if we go back to our previous example, the user has to scan again Shelf 1 just before to scan Product B if they really wants to take it from there.

[task-3007755](https://www.odoo.com/web#id=3007755&cids=1&menu_id=4720&action=333&active_id=966&model=project.task&view_type=form)

This update fixes an issue where field names were not shown correctly in the Pivot and Map sidebars in Odoo Studio. Users configuring these views will now see the correct field labels, reducing confusion and setup errors.

Since the new relational model ([65c8f41cf31787d30675ffd44fc955dae0102ee6](https://github.com/odoo/odoo/commit/65c8f41cf31787d30675ffd44fc955dae0102ee6)), the display name of the fields in Pivot and Map side bar was not fetched correctly as the active fields were not properly set.

This update replaces an older internal method for marking trusted web content with the current standard across several Odoo apps. It helps keep the codebase easier to maintain without changing day-to-day user workflows.

Use owl.markup instead

Part of task~3439226

Progressive web app capabilities, web push notifications, and vCard support have been moved from Enterprise to the community edition. This makes these mobile-friendly and notification features available more broadly while simplifying the Enterprise codebase.

In this commit, we moved all features related to the PWA and the PWA itself to the community.

This includes:
* PWA
* Web Push Notification
* VCARD

Task ID: 3478014

Forward-Port-Of: odoo/enterprise#47208 Forward-Port-Of: odoo/enterprise#47123

Forward-Port-Of: odoo/enterprise#47208
Forward-Port-Of: odoo/enterprise#47123

NCM code used for products in the unit tests where not longer available on testing environment making the unit test to fail, Change it the NCM code to some one avaiable on the Testing Webservice today. Forward-Port-Of: odoo/enterprise#46651

NCM code used for products in the unit tests where not longer available on testing environment making the unit test to fail, Change it the NCM code to some one avaiable on the Testing Webservice today.

Forward-Port-Of: odoo/enterprise#46651

Steps to reproduce: - Enable analytic account in accounting settings - Open any subscription - Once an invoice has been created it's not possible to edit analytic account Bug: Changing analytic account should be allowed for subscription opw-3280895 Forward-Port-Of: odoo/enterprise#46493

Steps to reproduce:
- Enable analytic account in accounting settings
- Open any subscription
- Once an invoice has been created it's not possible to edit analytic account

Bug:
Changing analytic account should be allowed for subscription

opw-3280895

Forward-Port-Of: odoo/enterprise#46493

PURPOSE Be defensive when dealing with email fields, notably when having multi-emails or email field containing an already-formatted email. SPECIFICATIONS When possible, use 'email_formatted' field on partner, instead of calling 'format_addr'. That way management of corner case input (multi emails and double encapsulation) is managed by the computed field itself. When 'format_addr' has to be used, ensure email part is normalized to avoid formatting issues. Post-message hook is

PURPOSE

Be defensive when dealing with email fields, notably when having multi-emails
or email field containing an already-formatted email.

SPECIFICATIONS

When possible, use 'email_formatted' field on partner, instead of calling
'format_addr'. That way management of corner case input (multi emails and
double encapsulation) is managed by the computed field itself.

When 'format_addr' has to be used, ensure email part is normalized to avoid
formatting issues.

Post-message hook is used in various apps to link records to a newly created
created partner. This is the case notably when used with a template as it
creates partner on the fly based on emails to always handle partners.
We now check either the complete 'email', either the normalized version of
it to avoid comparison issues with multi emails and formatted emails. As
'email_normalized' now supports multi-emails by storing the first found one
it helps finding the partner.

See sub-commits and community PR for more details.

Task-2612945 (Mail: Defensive email formatting)

Forward-Port-Of: odoo/enterprise#47158
Forward-Port-Of: odoo/enterprise#41828

This commit: - updates the DE balance sheet structure to use the correct one. - updates the account tags used for l10n_de. - updates the CoA for l10n_de. Community PR: https://github.com/odoo/odoo/pull/126249 task-3336261 Forward-Port-Of: odoo/enterprise#47066 Forward-Port-Of: odoo/enterprise#43077

This commit:
- updates the DE balance sheet structure to use the correct one.
- updates the account tags used for l10n_de.
- updates the CoA for l10n_de.

Community PR: https://github.com/odoo/odoo/pull/126249

task-3336261

Forward-Port-Of: odoo/enterprise#47066
Forward-Port-Of: odoo/enterprise#43077

How to reproduce the issue: -try to validate an invoice with an & in the RFC Update function _l10n_mx_edi_get_sat_status to be able to validate invoice with & in the RFC of customer or supplier Forward-Port-Of: odoo/enterprise#46862 Forward-Port-Of: odoo/enterprise#46836

How to reproduce the issue:
		-try to validate an invoice with an & in the RFC

	Update function _l10n_mx_edi_get_sat_status to be able to validate invoice with & in the RFC of customer or supplier

Forward-Port-Of: odoo/enterprise#46862
Forward-Port-Of: odoo/enterprise#46836

Studio field names may contain special characters that break the payroll report sql query. They should be wrapped in quotes. example field name: `x_l10n_sa_ot200%` ``` psycopg2.errors.SyntaxError: syntax error at or near "." LINE 27: ...ISTINCT FROM min_id.min_line THEN x_l10n_sa_ot200%.total ELS... ^ ``` Forward-Port-Of: odoo/enterprise#46668 Forward-Port-Of: odoo/enterprise#46624

Studio field names may contain special characters that break the payroll report sql query. They should be wrapped in quotes.

example field name: `x_l10n_sa_ot200%`
```
psycopg2.errors.SyntaxError: syntax error at or near "."
LINE 27: ...ISTINCT FROM min_id.min_line THEN x_l10n_sa_ot200%.total ELS...
                                                              ^
```

Forward-Port-Of: odoo/enterprise#46668
Forward-Port-Of: odoo/enterprise#46624

This reverts commit d166bc6aa9c53e487bb3190996a341f51133a62b. Since this commit it's not possible to edit a cell anymore. It will traceback directly due to comparaison between Date and Datetime opw-3496304,3496154 Forward-Port-Of: odoo/enterprise#47161

This reverts commit d166bc6aa9c53e487bb3190996a341f51133a62b.

Since this commit it's not possible to edit a cell anymore. It will traceback directly due to comparaison between Date and Datetime

opw-3496304,3496154

Forward-Port-Of: odoo/enterprise#47161

before this commit, on neutralizing a db, the ship rocket credentials are not reset with dummy values and live credentials will still exists in a neutralized db. after this commit, on neutralizing a db, the shiprocket credentials will be cleared from delivery carrier Forward-Port-Of: odoo/enterprise#46969

before this commit, on neutralizing a db, the ship rocket credentials are not reset with dummy values and live credentials will still exists in a neutralized db.

after this commit, on neutralizing a db, the shiprocket credentials will be cleared from delivery carrier

Forward-Port-Of: odoo/enterprise#46969

Before this commit, on a renewal quotation, changing the pricelist to a another one with different currency were not updating the order lines prices correctly. Now, when the pricelist is changed during a subscription renewal and the user clicks on the 'Update Prices' button, the prices are correctly recomputed and updated. This commit includes tests for ensuring this correct behavior. Additionaly, when a rule defined for a pricelist was selected it wasn't being taken into account in priority

Before this commit, on a renewal quotation, changing the pricelist to a another one with different currency were not updating the order lines prices correctly. Now, when the pricelist is changed during a subscription renewal and the user clicks on the 'Update Prices' button, the prices are correctly recomputed and updated. This commit includes tests for ensuring this correct behavior.

Additionaly, when a rule defined for a pricelist was selected it wasn't being taken into account in priority because rules without pricelist were being selected to get the lowest price. Now, the selected pricelist and its time-based pricing rule is taken into priority in the new order line calculation. This solution part was obtained by backporting a fix (task-id 2939221) and its unit tests.

Also, before this commit, when the 'Recurrence' field of a subscription was updated, the 'Unit Price' field of subscription products order lines was not being recomputed and the same field for regular products (non recurring) order lines was being recomputed. After this commit, after changing the 'Recurrence field', the price is recalculated only for subscription products. Unit tests were added for ensuring this correct behavior.

Finally, the 'Unit Price' for product variants was not being calculated properly when the variants had a specific time-based pricing, for instance two variants V1 and V2 with different pricing and the 'Recurrence' field as 'Monthly', when added to the subscription, both of them had their 'Unit Price' field defined as the product default price. After this commit, the 'Unit Price' calculation for variants is working properly.

Task-id: 3253969

Forward-Port-Of: odoo/enterprise#47113
Forward-Port-Of: odoo/enterprise#39245

A call was made to _build_column_dict() to construct the columns in this function. It shouldn't. Those are the columns used in the options and shouldn't be built with the same function. Forward-Port-Of: odoo/enterprise#46707

A call was made to _build_column_dict() to construct the columns in this
 function. It shouldn't. Those are the columns used in the options and
 shouldn't be built with the same function.

Forward-Port-Of: odoo/enterprise#46707