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

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

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