The payroll dashboard now uses a newer rich text field component and updated data handling behind the scenes. This should make dashboard content more reliable and easier to maintain without changing the overall payroll workflow for users.

Make use of the new html field component in the dashboard + and also the relational model hook and api instead of relying on plain objects.

This update replaces outdated form layout styling with newer supported layout classes across several Odoo apps. It helps keep pages compatible with the current design framework and also fixes alignment issues in the VoIP transfer call popup.

The quality worksheet validation screen and quality domain field have been modernized using Odoo’s newer interface framework. This should improve maintainability and help keep quality control workflows consistent with the rest of the platform, with minimal direct change for end users.

This commit converts both the `worksheet_validation` form and the `quality_domain_field` to OWL
TaskId: 2986089

Timesheet entries now verify that the linked employee is active when they are created. This helps prevent records from being logged against inactive employees, improving data accuracy across timesheet-related workflows.

At creation of aal, check that timesheets have an active employee.

task-2884736
Related PR: odoo/odoo#93823

Odoo Sign can now add an optional branded frame to signature areas showing that the document was signed with Odoo. The frame includes a signer-specific verification hash, with part shown near the signature and the full value added at the end of the document, improving trust and traceability.

Add an optional 'Signed with Odoo signed' frame on sign items.
These frame also feature a hash unique to the signer
(signer email + db_uuid) which is partially present on the frame
and present at the end of the document.

task-id : 2946442

CRM dashboard spreadsheets have been refreshed to provide more current and useful views of leads and pipeline performance. This helps teams monitor sales activity and make decisions with clearer dashboard information.

Knowledge articles now use the newer emoji picker when users choose or change an article icon. The experience remains familiar while adding a clear option to remove an existing icon directly from the picker.

This commit replaces the legacy emoji picker by the new
emoji picker in knowledge.

The emoji picker is triggered by the same user interactions
as the legacy emoji picker, i.e. click on an icon in a
knowledge article.

Knowledge emoji picker has the default behaviour of base
emoji picker, and then slightly extends with a action to
remove the icon of emoji. This remove action is a button
in the header part of emoji picker.

Task-2980528

Community: https://github.com/odoo/odoo/pull/100010

Tasks created from documents now include a log note, making it easier for teams to understand where work originated. Planning shifts created from a task's planned hours action now use the task dates by default, reducing manual entry and helping schedules stay aligned.

** = project_forecast,planning

Purpose of this commit to improve generic usage of project
app.

So, in this commit done following changes:
- add log note for tasks created from documents
- add default dates for Hour Planned button's action to set default
dates on newly created shifts according task's dates.

task-2853991

Task bars in Gantt views now show start time, end time, allocated hours, and task name when the planned work is under 24 hours. This makes short tasks easier to understand at a glance, and project contract buttons are hidden when no related contract exists.

-When the task plan is less than 24 hours, the start hours, end hours, and
allocated hours and the name of the task will appear in the gantt view in
the pill title.

Example- '7:00 AM - 11:00 AM (4h) - DST Task 1'

Currently this features is only in planning.

Create a new services_web_gantt module and it's used in planning and
project_enterpise modules.

-If the project does not have a link to any of the contracts then
the contracts stat button will not appear in the project form view.

task-2672783

This update improves the Field Service task creation experience by placing a helper tip in a more useful position. It also makes worksheet settings more reliable by disabling worksheets by default for non-Field Service projects and stabilizing related automated checks.

In this commit:
- The tip for the partner in create task step is changed from buttom to right
- project.project: the 'worksheets' option should be set to false by default if is_fsm is false.
- test_project_worksheet_template_propagation fail if a default_worksheet is set as we are asserting fsm_project.worksheet_template_id but when creating fsm_project, if a default_worksheet is set, when _compute_worksheet_template_id is called, the project worksheet_template_id will be set as the default_worksheet, to avoid this instability, we assert that fsm_project and its task have the same worksheet_template_id at the beginning of the test to work on both cases (No worksheet, Default worksheet)

Task-2849270

The Appointment, Knowledge, Planning, and Sign apps are now configured to install automatically when their requirements are met. This reduces manual setup work and helps businesses activate related workflows more smoothly.

Financial reports now keep popup icons visible even when a leading value is zero or otherwise appears empty. This prevents users from losing access to actions such as carryover details or cell editing while still preserving the report layout behavior.

When rendering the report, we remove some empty column values in order to let space to stretch the line name further. When doing that, we didn't check whether the line contained a popup icon or not (for carryover or cell edition, for example), causing them to disappear on 0-balanced leading cells.

The phone number input now uses the correct standard field type, improving consistency with browser behavior. This helps ensure phone fields work as expected across devices and avoids relying on an invalid input setting.

This pr is the enterprise counter part of odoo/odoo#100388 where we set the input type to "tel" in PhoneField, instad of "phone", which simply doesn't exist.

Graph and pivot views now receive the extra field information they need to show all valid measure and grouping choices. This helps users build reports more reliably without missing available numeric measures or groupable fields, while test tooling was updated to match the server behavior.

Following odoo/odoo@4636620004f0cc0e504cd6694fe8ddb6758ba811 `get_views` only pass the model fields included in the view architecture, except for the main model when the search views is requested. Because the search views requires all fields for the user to be able to make advanced filters and advanced group by using any fields of the model.

However, other views requires more field descriptions as well than just the fields included in their architecture:
- the graph view requires all integer and float fields, to automatically add suggestions of measures in the measures dropdown menu. It's a bit like the search view, the user should be able to choose any measure available in the model (as long as this is integer or float fields)
- the pivot view requires all groupable fields, so the user can group by any groupable fields of the model.

The JS MockServer `getViews` is adapted to include the changes added by the above revision as well as the current revision,
for the qunit tests suite to be able to reflect these API changes from the server side.

This fixes an issue where the report export wizard did not work correctly when the Documents Accounting app was installed. The problem came from a class being moved to the wrong place during refactoring, and a new test was added to help prevent the issue from returning.

When documents_account was installed, the report export wizard was not working properly.

During a refactoring, a class was incorrectly moved.

A test is added to prevent that to happen again.

Signed-off-by: Ruben Gomes <rugo@odoo.com>

This fixes missing styling for PDF previews in manufacturing work orders and Sign after an internal field name changed. Users should see PDF documents displayed with the expected layout again, improving readability and consistency.

The class for the pdf_viewer field changed from `o_field_pdfviewer` to `o_field_pdf_viewer`

Opening the balance from the bank reconciliation widget now works without causing an error. This restores a normal accounting workflow after an internal reporting change broke the link.

…ank reconciliation report

- Go to the bank reconciliation widget
- Click on the balance on the top
=> Traceback

There are two issues here:
1) The action no longer exists since the refactoring of account_reports
2) Even if fixed, We are referencing an action defined in account_reports that is not a dependency of account_accountant.

This fixes the appearance of certain dropdown fields in salary contract pages after the Bootstrap 5 migration caused them to display with mismatched styling. Users should see a more consistent and familiar form experience while a longer-term library upgrade remains for the future.

Due to the migration of Bootstrap 5, `form-control` was converted into `form-select` to `select` tag. This made was due to a caret missmatch with the previous version due to a change in Boostrap 5.

But in some case the `select` input used Select2. Actually our Select2 is an old version (3.5.4 the last release is 4.0.13) and we have a `CSS` file alongside Select2 to match the style of Boostrap, but it is for Boostrap 3. We restore the old class in these case to restore the old styling (with little hiccup but better than actual).

The good fix, will be to upgrade the lib, and its Bootstrap theming (for BS5) to the last version.

This update adjusts several accounting, localization, rental, signing, and Studio features to work correctly with Odoo's newer translation storage format. It helps preserve translated content reliably when reports, views, and related tools are edited or tested.

Shipments with no insurance amount will no longer trigger an unnecessary insurance request to EasyPost. This prevents failed shipping operations caused by EasyPost rejecting insurance amounts of zero.

Before this commit, we call the `/insure` endpoint even when it is null.

this leads to the following error:
`Easypost returned an error: Insurance amount must be greater than 0`

With this commit, we avoid calling the insure endpoint whenever the insured amount is 0.0 .

This fixes the Hungarian balance sheet and profit and loss report definitions so financial statements are generated more accurately. It helps Hungarian companies rely on Odoo reports for compliance and business reporting.

Fix balance sheet and profit and loss for Hungarian localization

Task-id: 2816907

Signed-off-by: Ruben Gomes <rugo@odoo.com>

This fixes an issue where PDF support was not loading properly in the Documents app after recent asset bundle changes. Users should once again see PDF thumbnails and previews behave as expected when working with documents.

After the changes to bundles recently the pdf js bundle was not loaded properly within the documents app.

Installing the Chilean localization reports module no longer causes an error when users open Settings. This fix keeps the configuration page accessible, reducing disruption for companies using Chile-specific reporting.

Installing l10n_cl_reports would lead to a JS error upon opening Settings. The error seems to be due to an 'o_settings_container' being defined inside another. This commit fixes this.

It's not clear to me why this error only appeared now, and not in previous versions.

Task 2968918

The spreadsheet document filter selector was updated to align with the newer interface components used across Odoo. This is an internal modernization that should keep the same user experience while improving maintainability and consistency for future updates.

Forward-Port-Of: odoo/enterprise#31370

Forward-Port-Of: odoo/enterprise#31370

Forward-Port-Of: odoo/enterprise#31042

Forward-Port-Of: odoo/enterprise#31042

Forward-Port-Of: odoo/enterprise#31116

Forward-Port-Of: odoo/enterprise#31116

Before this commit, recurrence_id is required for subscription views and not in sale_management. As some upgraded upsells have no recurrence_id, make it the recurrence_id required for all so in sale_subscription application cause issues. Forward-Port-Of: odoo/enterprise#31249

Before this commit, recurrence_id is required for subscription views and not in sale_management. As some upgraded upsells have no recurrence_id, make it the recurrence_id required for all so in sale_subscription application cause issues.

Forward-Port-Of: odoo/enterprise#31249