Users can now unschedule project tasks directly from the Gantt popover, without opening the edit screen first. This reduces clicks and speeds up repeated scheduling adjustments for project teams.

Before this commit:
- Having to unschedule a task is quite common. Having to click on the pill to open the popover,
then click on edit and then click on unschedule is annoying, especially when you have to do it for multiple tasks in a row.

After this commit:
- project.task gantt view popover: an 'unschedule' button is added in secondary in the popover

task-3475170

Failed quantities on stock pickings can now be redirected to a dedicated failure location for further processing, improving traceability and follow-up. Quality worksheet checks also open more directly, reducing extra steps for users during inspections.

This commit adds the ability to change the destination of a failing quantity
to a failure location for futhur processing. This is done by creating a
new move line for the failed qty using `_move_line_to_failure_location`

In `quality_control_worksheet` if a check is of type worksheet, the worksheet
will open directly without showing the wizard first.
Also some spring cleaning was done to remove copied code from the quality wizard.

TaskId: 3380442
Community PR: https://github.com/odoo/odoo/pull/130002
Upgrade PR: https://github.com/odoo/upgrade/pull/5194

Accounting reports now use one consistent company selection field, whether users report on one company or several. This simplifies report handling across accounting and localization modules and improves how company names appear in PDF exports.

*: account_asset,account_disallowed_expenses,l10n_es_reports,l10n_eu_oss_reports,l10n_lu_reports,l10n_mx_xml_polizas,l10n_nl_reports_sbr,l10n_pe_reports,l10n_sg_reports,mrp_account_enterprise,mrp_workorder_hr_account

Main changes
1. Report options:
   Instead of storing either a 'multi_company' or 'single_company' key just store a 'companies' key.
2. Simplify the template 'pdf_export_filters' from 'account_reports'
3. Adapt calls to function '_get_query_currency_table' of model 'res.currency'.
   Due to 1. this function was refactored (see community PR).

on 1.
-----
The new 'companies' key is used to store all the active companies (even if there is only one).

This is the main change. The other changes were possible (2.) or
needed (3.) due to this change.

All the modules depending on it had to be adapted accordingly.

on 2.
-----
The printing of the company names was simplified.
The render value 'report_company_name' that was only used to print the company name in the
"single company" case was removed.

on 3.
-----
Due to change 1 the '_get_query_currency_table' function of the
res.currency model (added in module 'account' from the community repository) was refactored:
It does not use the report options as argument anymore (see community PR).
A helper function '_get_query_currency_table' was introduced in model 'account.report' that just takes
the report options as a parameter and calls '_get_query_currency_table' with the proper arguments.
All calls to '_get_query_currency_table' were adapted

task-3484368

Community PR: https://github.com/odoo/odoo/pull/136173
Enterprise PR: https://github.com/odoo/enterprise/pull/47735

Maintenance teams can schedule maintenance directly on work centers and automatically block production work orders during those time slots. This helps planners avoid conflicts, see downtime in planning views, and manage multiple recurring maintenance schedules for the same work center or equipment.

Allow to perform maintenance operations on workcenters.
Block workorders during maintenance slots.
Workcenters now gather maintenance data.

task: 2444754

Department cards in the appraisal area now open only the records linked to the selected department. This makes it easier for managers and HR teams to find the right appraisal information without manually filtering unrelated records.

In this commit, we have enhanced the functionality of department kanban view actions. Now, when you click on an action, it will open only the records associated with the corresponding department.

Task ID: 3541358

The Help Center now presents forum posts, knowledge articles, and courses in separate, easier-to-scan quick-link lists. This helps visitors find the most relevant support content faster by highlighting popular or recently active items.

* = forum, knowledge, slides

This commit aims to make the help center better looking by using separated lists of quick-links to items such as forum posts, knowledge articles and courses.

Each list has at most 5 elements and they are sorted based on votes / activity date for the forum posts, favourites / write date for the knowledge articles and number of views for the courses.

task-3444600

Maintenance teams can now use worksheet templates directly on maintenance requests, helping standardize work instructions and capture consistent information. The request form also gains dedicated Notes and Instructions tabs, making key guidance easier to find and use during maintenance work.

Manage worksheet templates on maintenance requests.

Also add 'Notes' and 'Instruction' tabs in form view.

task: 3186753

Marketing Automation now includes predefined demo campaign templates that customers can use to set up campaigns and activities faster. The change also ensures these sample templates are only loaded when requested and avoids duplicate campaign actions.

The goal of this commit is to create demo data,
predefined templates will be introduced,
which can be used by customers to quickly
create marketing campaigns and their activities

The commit uses `convert_file` function in order
to avoid loading demo data unless they are requested.
Additionally, actions are created with their xmlids in
order to avoid having duplicate actions.

task-3186815

Fixed an issue in the manufacturing work order flow where saving from the quality check production registration button could fail. This helps operators complete quality checks and production registration more reliably without workflow interruptions.

Fix to ensure that calling save() works on model.root.records which is now an Array of Proxy(Record) and not simply a Proxy(Record).

This work-in-progress change adjusts an automated test for spreadsheet chart settings in Documents. It is intended to improve test reliability and does not introduce a direct user-facing change.

WIP - Please ignore this PR

This update replaces older date and time handling with newer shared utilities across several Odoo areas. It helps keep the platform easier to maintain while preserving expected behavior for users working with documents, barcode flows, and VoIP-related activity data.

The purpose of this commit is to delete the legacy/js/core/time.js file. We have therefore replaced all calls to time.js with the l10N/date.js utilities.

Part of task 3439226

This commit resolves an issue where payroll officers were encountering an access error when attempting to open the payroll app for a Belgiam company. The problem was addressed by including the necessary payroll officer rights within the l10n_be_hr_payroll module. task : 3497448 Forward-Port-Of: odoo/enterprise#48742 Forward-Port-Of: odoo/enterprise#48010

This commit resolves an issue where payroll officers were encountering an access error when attempting to open the payroll app for a Belgiam company. The problem was addressed by including the necessary payroll officer rights within the l10n_be_hr_payroll module.

task : 3497448

Forward-Port-Of: odoo/enterprise#48742
Forward-Port-Of: odoo/enterprise#48010

Add a smart button on child assets, to retrieve the parent. Remove the New button on child assets Only show the form view if only one gross increase. task-3531619 Forward-Port-Of: odoo/enterprise#48638

Add a smart button on child assets, to retrieve the parent. 
Remove the New button on child assets
Only show the form view if only one gross increase.

task-3531619

Forward-Port-Of: odoo/enterprise#48638

Versions: --------- - saas-16.4 - master Steps to reproduce: ------------------- 1. go to Planning / Settings; 2. enable Project Planning; 3. go to Planning / Schedule / By Resource; 4. click New; 5. create a new project via the form and save; 6. click New again; 7. try to find the recently created project. Issue: ------ The project you just created is nowhere to be found. Cause: ------ https://github.com/odoo/odoo/pull/122144 removed the requirement for projects to have

Versions:
---------
- saas-16.4
- master

Steps to reproduce:
-------------------
1. go to Planning / Settings;
2. enable Project Planning;
3. go to Planning / Schedule / By Resource;
4. click New;
5. create a new project via the form and save;
6. click New again;
7. try to find the recently created project.

Issue:
------
The project you just created is nowhere to be found.

Cause:
------
https://github.com/odoo/odoo/pull/122144 removed the requirement for projects to have a `company_id`, so by default this field is False.
Planning still requires a `company_id` and the `project_id` field assumes `project.project` does so as well, as its domain is `[('company_id', '=', company_id)]`

Solution:
---------
The field already has `check_company=True` enabled which automatically adds the desired domain check allowing `('company_id', '=', False)` as of https://github.com/odoo/odoo/commit/0d30cc2bc9b9cc2b805d6c2d0a440f185c648da0, so removing the more restrictive domain in the field definition solves the issue.

opw-3519857

Forward-Port-Of: odoo/enterprise#48813

This commit is the enterprise side of this: odoo/odoo#135142 It modifies a test to ensure custom GS1 separators are correctly used client side. Community PR: odoo/odoo#135142 Forward-Port-Of: odoo/enterprise#48487 Forward-Port-Of: odoo/enterprise#47292

This commit is the enterprise side of this: odoo/odoo#135142 It modifies a test to ensure custom GS1 separators are correctly used client side.

Community PR: odoo/odoo#135142

Forward-Port-Of: odoo/enterprise#48487
Forward-Port-Of: odoo/enterprise#47292

When we pass our mouse on the connected until widget if the text is too big for the place in the div, the widget flickers. It's not visually pleasant. We fix the issue by using a `text-nowrap` class on the div. NB: To fix completed the flickering, we have to remove the useless d-flex on the main div. To avoid breaking the stable policies, we'll fixing it in master only. task-id: 3556087 Forward-Port-Of: odoo/enterprise#48997

When we pass our mouse on the connected until widget if the text is too big for the place in the div, the widget flickers. 
It's not visually pleasant.
We fix the issue by using a `text-nowrap` class on the div.

NB: To fix completed the flickering, we have to remove the useless d-flex on the main div. To avoid breaking the stable policies, we'll fixing it in master only.

task-id: 3556087

Forward-Port-Of: odoo/enterprise#48997

- Install l10n_es_reports - Go to Accounting/Configuration/Accounting Reports (in debug) - Go to PYMES Balance Sheet - You see the Accounts Coverage Report while you don't have the right COA. => If availability_condition is 'coa', check the COA. It will be especially important when we do the same for SYSCOHADA, where we don't have any country, but we have a COA, in task 3456480 Forward-Port-Of: odoo/enterprise#48966 Forward-Port-Of: odoo/enterprise#47933

- Install l10n_es_reports
- Go to Accounting/Configuration/Accounting Reports (in debug)
- Go to PYMES Balance Sheet
- You see the Accounts Coverage Report while you don't have the right COA.

=> If availability_condition is 'coa', check the COA. 
It will be especially important when we do the same for SYSCOHADA, 
where we don't have any country, but we have a COA, in task 3456480

Forward-Port-Of: odoo/enterprise#48966
Forward-Port-Of: odoo/enterprise#47933

Steps to reproduce the error: 1. Enable the developer mode. 2. Go in "Settings" > "Technical" > "Template" in the Knowledge section. 3. Delete all templates. 4. Go on Knowledge. 5. Click on the "Browse Templates" button. => An error is thrown because the `onMounted` hook defined in the dialog of the template gallery tries to access an element that is not present in the dom. TO BE: The system should not display any error message. Instead, the template dialog should open, informing the

Steps to reproduce the error:
1. Enable the developer mode.
2. Go in "Settings" > "Technical" > "Template" in the Knowledge section.
3. Delete all templates.
4. Go on Knowledge.
5. Click on the "Browse Templates" button.

=> An error is thrown because the `onMounted` hook defined in the dialog of the template gallery tries to access an element that is not present in the dom.

TO BE: The system should not display any error message. Instead, the template dialog should open, informing the user that there is no templates available.

task-3542906

Forward-Port-Of: odoo/enterprise#48546

If one imports journal items with a file, where one of the move_id name has a long number, e.g. SAL/2021/123454234587345, the import fails when creating a move with such a big sequence number. Limiting length of the sequence number fixes the issue task-3549609 Forward-Port-Of: odoo/enterprise#48794

If one imports journal items with a file, where one of the move_id name has a long number, e.g. SAL/2021/123454234587345, the import fails when creating a move with such a big sequence number. Limiting length of the sequence number fixes the issue

task-3549609

Forward-Port-Of: odoo/enterprise#48794

This commit's purpose is to place a bit more space between the tags and the name of the product in the products catalog for fsm tasks. details of the implementation : The margin and padding did not have any effect on the 'strong' and the 'span' tag. The 'priority' widget was moved instead. Since adding marging/padding to it was moving the whole div and not only the widget, the d-flex class was added to the container div. task - 3489879 https://www.odoo.com/web#id=3489879&menu_id=4720&

This commit's purpose is to place a bit more space between the tags and the name of the product in the products catalog for fsm tasks.

details of the implementation :

The margin and padding did not have any effect on the 'strong' and the 'span' tag. The 'priority' widget was moved instead. Since adding marging/padding to it was moving the whole div and not only the widget, the d-flex class was added to the container div. 

task - 3489879
https://www.odoo.com/web#id=3489879&menu_id=4720&cids=1&action=333&active_id=4105&model=project.task&view_type=form

Forward-Port-Of: odoo/enterprise#48172

Steps to reproduce - in the CRM pivot view, group by create_date > saleperson - insert in a spreadsheet - Try to autofill this formula: =PIVOT.HEADER(1,"create_date:month","04/2022","#user_id",2) => boom That's because only `["#user_id", 2]` was given to `getDisplayedPivotHeaderValue`, instead of the full group path `["create_date:month","04/2022","#user_id",2]` Task: 2886599 Forward-Port-Of: odoo/enterprise#48825 Forward-Port-Of: odoo/enterprise#48797

Steps to reproduce
- in the CRM pivot view, group by create_date > saleperson
- insert in a spreadsheet
- Try to autofill this formula: =PIVOT.HEADER(1,"create_date:month","04/2022","#user_id",2) => boom

That's because only `["#user_id", 2]` was given to `getDisplayedPivotHeaderValue`, instead of the full group path `["create_date:month","04/2022","#user_id",2]`

Task: 2886599

Forward-Port-Of: odoo/enterprise#48825
Forward-Port-Of: odoo/enterprise#48797