Users can now save spreadsheets as reusable templates, making it faster to create recurring reports with the same structure and formatting. Templates avoid tying pivot-based reports to old database records and clean up empty pivot rows when reused, helping reports adapt better to current business data.

Purpose
=======
Creating nice and usefull spreadsheet reports can be challenging and time
consuming. Moreover many reports can be very similar.
e.g. "Budget 2019" and "Budget 2020" most probably share the same structure.
This commit introduces a way to easily reuse a report structure: spreadsheet templates.

With spreadsheet templates we can also provide "pre-made" templates designed by
Odoo. With those templates, users can quickly dive into spreadsheets and
spreadsheet reports.

Specification
=============

Allow to create a spreadsheet template from a spreadsheet with an additional
top bar menu: "File > Save as template".

A template should keep everything from the original spreadsheet (content, style,
conditionnal formattings, formulas, etc.), except `PIVOT` formulas.

`PIVOT` formulas need some extra care since they are strongly bound to the
actual records in the database. In particular, some records are directly
referenced by their id.
e.g. revenue by team `=PIVOT("1","amount","team_id","5")`.

Since templates should be independent from any actual data, no specific record
is ever referenced by a template. When a new spreadsheet is created from a
template, real records actually in the database are used. They are retrieved in
the same order the original pivot would have retrieved them.

Let's consider the following example:
We have two teams: team "1" with 6 employees and team "2" with 3 employees.
And the following pivot, grouped by team, ordered by the number of team
members. The pivot is saved as template.

```
 -----------------
|        | Income |
 -----------------
| Team 1 |  1234  |
 -----------------
| Team 2 |  5678  |
 -----------------
```
Later (or in another database), a new spreadsheet is created from the template.
Team "1" no longer exists (or never existed), team "2" has now 10 employees
and we have another team: team "8" with 4 employees. Teams "2" and "8" will
appear where teams appeared in the original spreadsheet but ordered according
to the actual data.

```
 -----------------
|        | Income |
 -----------------
| Team 2 |  5678  |
 -----------------
| Team 8 |  7412  |
 -----------------
```
Limitations
===========
1) The number of "pivot slots" in a template is fixed at creation.
   If there are two teams when the template is created, only a maximum of two
   teams will be shown when the template is later used, even if more teams were
   created in the meantime. This limitation can be workedaround in the case of
   "pre-made" templates by Odoo. We can artificially add more teams when we
   create the template. The number is arbitrary though and will not fit all
   use cases. This can also be workedaround by autofilling the pivot formulas
   once the spreadsheet is created, but the autofill feature has its own
   limitations.

2) ...

Task 2281013

Co-authored-by: fleodoo <fle@odoo.com>
Co-authored-by: LucasLefevre <lul@odoo.com>

Map views can now group records, making it easier for users to compare locations by category with clear group coloring. The map template also supports a configurable record limit, allowing businesses to control how many items are loaded and shown in the pager.

This PR adds the possibility to group the records in map view and adds the parameter `limit` to map's template to change the size of pager

This update improves how the system looks up related records, reducing the number of database requests needed for common searches. It should make several business workflows feel faster and more scalable without changing day-to-day functionality.

Companion of https://github.com/odoo/odoo/pull/52403.

CRM reporting views now hide fields that are not meaningful as measures, making dashboards, cohort, graph, and pivot analysis easier to use. This reduces clutter in reporting dropdowns and keeps dashboard behavior consistent when fields are hidden from standard analysis views.

PURPOSE

Support invisible attributes to remove irrelevant fields in standard views.

SPECIFICATIONS

Add the possibility to not display some fields in the measures dropdown for
the cohort views.

When a field is not displayed in the measures of a pivot views we remove them
also from the list of groupable fields.

Update CRM addons to hide irrelevant measures.

LINKS

Task ID-2288381
Community PR #54774
Enterprise PR odoo/enterprise#11970
Upgrade PR odoo/upgrade#1519

The reporting menus for Planning, Field Service, and Project timesheet planning now show clearer helper messages. This helps users better understand what each report is for and how to use it when navigating service-related reporting areas.

Mass mailing templates were cleaned so preview screens better reflect the intended email content. Decorative images no longer show unnecessary alternative text, reducing visual clutter and making previews clearer for users preparing campaigns.

Purpose
=======
Clean the mass mailing templates to have a better preview.
(e.g. Remove the alt attribute of the images which are not
part of the mail content)

Task-2313872

Employees now appear with clickable profile pictures in key grid and Gantt planning views when grouped by employee. This makes it easier for users to identify colleagues and start a chat directly from timesheets, leave, appraisal, planning, and forecast schedules.

Taskid: 2272544
Taskid: 2272582
PR https://github.com/odoo/odoo/pull/54230

This PR take over the following https://github.com/odoo/enterprise/pull/11283 which can be discarded

Description of the issue/feature this PR addresses:
> The new avatar widget allows to chat with other users by clicking on their profile picture.
> This widget is working in kanban, list and form views, but not in grid and gantt views.

Current behavior before PR:
> No avatar widget with click function on these views

Desired behavior after PR is merged:
> Employees are now showed using the avatar widget on following grid and gantt views (when they are at anypoint grouped by employee):
> - timesheet_grid.timesheet_view_grid_by_project
> - timesheet_grid.timesheet_view_grid_by_employee
> - timesheet_grid.timesheet_view_grid_by_task_readonly
> - hr_holidays_gantt.hr_leave_gantt_view
> - hr_holidays_gantt.hr_leave_allocation_gantt_view
> - hr_holidays_gantt.hr_leave_report_calendar_view_gantt
> - hr_appraisal.hr_appraisal_view_gantt
> - planning.planning_view_gantt
> - project_forecast.planning_view_gantt
> - project_timesheet_forecast.planning_view_gantt

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Gantt views can now show helper guidance over sample or empty data, making it clearer to users when displayed records are only placeholders. This improves consistency with list and kanban views and helps users understand what action to take next.

PURPOSE
Display action helper on top of Gantt dummy data to clarify that those are not real data.

SPEC
Display action helper on top of Gantt dummy data to clarify that those are not real data.

TASK 2284779

The planning view for selected tasks now correctly shows all chosen tasks, including those without scheduled planning entries. The forecast planning display also restores allocation percentages and progress bars, helping teams quickly assess workload and progress.

Fixed an issue that caused an error when managers used Send & Publish for open shifts. Open shifts are now correctly shared with eligible employees based on role settings, preventing disruption in scheduling workflows.

[FIX]planning: Traceback when sending an open shift

**Steps to reproduce:**
create an open shift > click on 'send & publish'

**Observed behavior:**
AssertionError: Invalid value res.company(1,) in domain term ('company_id', '='$

**Expected behavior:**
- No traceback
- The open shift is correctly sent to employees with
--> either 1) this role set by default 2) no roles set by default
--> or to all employees if no role is set on the shift

This update corrects how Belgian HR payroll and salary contract settings handle the default holiday field. It helps ensure payroll configuration uses the right setting consistently, reducing setup errors for Belgian payroll users.

apply given solution, make res_config_settings.py file in l10n_be_hr_contract_salary model.

This update removes incorrect reference data from the Colombian electronic invoicing module. It helps prevent businesses in Colombia from using invalid values in their e-invoicing workflows, reducing the risk of compliance or processing issues.

Task: https://www.odoo.com/web#id=2298403&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720

Odoo’s paid service integrations were reorganized into shared bridge modules so related apps can reuse the same foundations more consistently. This is mainly an internal cleanup that improves maintainability and reduces future migration risk, with compatibility kept for existing code during the transition.

Stock movement scheduling now uses a single date field instead of keeping a separate expected date. This reduces duplicate information and makes stock, manufacturing planning, and inventory reports easier to maintain, while the previous scheduled date is no longer retained once a move is completed.

In community, the date_expected fields was duplicated with the date fields
except when the move was done. Merge both fields.
The only information lost is: we can't know what was the
scheduled date before processing move (put in done).
Indeed, the date becomes the actual move processing.

task-2246665
odoo/odoo#55379
odoo/upgrade#1586

The manifest file introduced by the social push notifications module is now obsolete and not used anymore by the web push framework (Firebase). Tests have confirmed that web push notifications work perfectly without that file. We remove this file because, in addition to being useless, it can cause issues for other modules that want to add their own manifest file. (Ideally, the web application can only contain one manifest file). Remove * social_push_notifications.social_push_notifi

The manifest file introduced by the social push notifications module is
now obsolete and not used anymore by the web push framework (Firebase).
Tests have confirmed that web push notifications work perfectly without that
file.

We remove this file because, in addition to being useless, it can cause issues
for other modules that want to add their own manifest file.
(Ideally, the web application can only contain one manifest file).

Remove
  * social_push_notifications.social_push_notifications_layout

Task #2321050

Forward-Port-Of: odoo/enterprise#12472

task 327 --- Be able to let odoo partners to inherit the logic of when a dummy afip validation has to be done. Forward-Port-Of: odoo/enterprise#12047

task 327
---

Be able to let odoo partners to inherit the logic of when a dummy afip validation has to be done.

Forward-Port-Of: odoo/enterprise#12047