Documents spreadsheets now support links that can take users directly to Odoo menus, making spreadsheets a more practical navigation and reporting hub. The update also refreshes the spreadsheet engine and improves reusable selection components behind the scenes.

View validation has been streamlined so Odoo can check screens and customizations more efficiently. This should reduce delays during updates or configuration changes while keeping existing Gantt, Grid, and Studio behavior aligned with the core platform changes.

See https://github.com/odoo/odoo/pull/75796

Spreadsheet files in Documents now use Odoo's own spreadsheet icon, creating a more consistent product experience. The spreadsheet component was also refreshed with related visual and editing fixes, including composer design updates and improved handling of merged-cell highlighting.

PURPOSE:

The purpose of this task is to use our own icon design for spreadsheets.

SPECIFICATIONS:

update spreadsheet icon to odoo's spreadsheet icon.

LINKS:

Task-2477155

The Barcode app now makes quantity entry quicker with an on-screen number pad and packaging shortcuts in line edit forms. Products tracked by serial number are grouped under summary lines, reducing clutter for warehouse teams while keeping details accessible when needed.

Adds a digipad in `stock.move.line`/`stock.inventory.line` form view in the Barcode App.
Also, regroups the line tracked by serial number under the same group. The lines will be hidden under a summary line, and can be displayed by pressing a button.

The planning Gantt view now makes employee availability easier to understand. When an employee is not expected to work during a period, the progress bar is replaced with a warning icon and explanatory message, reducing confusion for schedulers.

This PR improves planning's gantt view's progress bar:

- Prevents the `lightened` effect introduced in PR #18045 on .o_gantt_row_title
- When the employee isn't expected to work, replace the progress bar by an 
  exclamation triangle icon and tell the user the employee isn't expected to 
  work during this period


task-2638342

The Field Service app data setup was corrected so it can be installed successfully even when demo data is not selected. This prevents installation failures and lets businesses deploy Field Service in clean production-style databases.

Before this commit:
When trying to install FSM without demo data, it gives traceback.

After this commit:
It will install FSM successfully without demo data.

Task-2632519

This change updates an internal performance test threshold for Belgian payroll accounting to avoid disruptive test failures during the release freeze. It does not change payroll functionality for users, but helps keep validation and delivery processes stable.

Although we hate to bump query count without a good reason, but this
one is annoying during the freeze.

Task created to fix it: #2638448

This change prevents the signing popup from opening accidentally when users resize or move signature fields while editing a sign request. It makes the signing flow smoother and avoids interruptions before fields are correctly placed.

In task-2475732, a feature was added that allowed users to edit sign requests while signing. This consists of adding sign items, moving them with drag and drop, resizing them and signing them after they are correctly placed. After signing a signature/initial field, it is not possible to move it or resize it.

Due to the differences in the HTML content between the editable sign item and the non-editable sign item, the click event registered to sign each item should be different. Currently, the click event is registered on the sign item itself, for both cases. However resizing/dragging causes the event to bubble up and trigger the click event in the sign item (afterall resize and drag-drop are just mousedown and mouseup events). This then causes the signature/opening of wizard everytime a resize or a drag is done in the added sign items.

This PR solves this problem with the following approach: register the click event in the "o_sign_config_area" element instead of the sign item, when the sign item is editable.

task-2636460

A failing automated test for appointment links is being skipped because it blocks other updates from being merged after a certain time of day. This is an internal change to keep development moving while the test issue can be addressed separately.

The appointment_link qunit test is failing after 17:00 and makes it
impossible to merge other things.

This issue can be reproduced by using faketime.

The appraisal feedback request now includes helpful placeholder text, making it clearer what should be entered before sending. This reduces confusion for managers or HR users when asking employees or colleagues for appraisal feedback.

task - 1251

The dedicated Project Overview and Project Costs and Revenues reports are removed because their information is available elsewhere and the old views were hard to improve. Project pages and updates now provide clearer links to related costs, revenues, and source documents so users can better understand what drives project performance.

The project overview is a significant technical debt 
as it is a custom qweb view. It is quite limited: 
- It is not possible to group the data, to filter on dates,
SOs or Field Service projects.
- Improving this is very difficult and would require weeks 
of development that are not worth it.
In any case, all the information provided by the project overview 
can be found elsewhere. The stat buttons of the report are basically 
duplicates of the ones from the project form view.
Therefore, we are removing this report and its twin, 
the Project Costs and Revenues.

In addition, analytic items lack context for the user to understand 
what generated a certain cost or revenue:
- there is no link to the source document;
- the entries are not categorized (e.g. it is not easy to understand 
if a cost comes from a timesheet cost, a purchase order or an expense);
- the billable type group by works fine for timesheets but then all 
the other entries are flagged as Undefined, which is not very helpful;
- there is no option to easily isolate costs from revenues.

task-2545084
See odoo/odoo#72736
See odoo/upgrade#2706

Task dependency information is being moved from the Enterprise project app into the standard community project app. This makes the dependency relationship available more broadly for future project management improvements while keeping current business impact minimal.

This commit moves the project.task dependent_ids field to the community
project module in order to take advantage of this relation for further
development.

See : odoo/odoo#76011

This update modernizes parts of Odoo's spreadsheet, dashboard, cohort, and web interface foundations to align with the newer user interface framework. Business users should see a more consistent experience in spreadsheets and dashboards, while the changes also prepare these areas for easier future improvements.

Generated attachments in the EDI system must be valid for the government Revert: https://github.com/odoo/enterprise/commit/f3571aed1ce12f05aa036ab0ab21d01dd5d123d5 https://github.com/odoo/enterprise/commit/06a82a94fc4310dcb9b0570717338891cfaaf33b https://github.com/odoo/enterprise/commit/0df2003d4a6018045ded3bc8864528ad88a81605 Forward-Port-Of: odoo/enterprise#20545 Forward-Port-Of: odoo/enterprise#20540

Generated attachments in the EDI system must be valid for the government

Revert:
https://github.com/odoo/enterprise/commit/f3571aed1ce12f05aa036ab0ab21d01dd5d123d5
https://github.com/odoo/enterprise/commit/06a82a94fc4310dcb9b0570717338891cfaaf33b
https://github.com/odoo/enterprise/commit/0df2003d4a6018045ded3bc8864528ad88a81605

Forward-Port-Of: odoo/enterprise#20545
Forward-Port-Of: odoo/enterprise#20540

The parameters order made it so that a res.partner was passed as the product. Forward-Port-Of: odoo/enterprise#20597

The parameters order made it so that a res.partner was passed as the product.

Forward-Port-Of: odoo/enterprise#20597