The appraisal module now presents appraisal records in a clearer, more actionable way by keeping key dates stable, prioritizing upcoming appraisals, and applying a default To Do view. Date displays and overdue indicators are also clearer, helping HR teams focus on appraisals that need attention without confusion from completed or cancelled items.

This commit introduces several improvements:
- The Appraisal Date is no longer automatically rewritten upon changing the state to Cancel or Done.
- The order of appraisals in the list view is adjusted to show those with the appraisal date closest to the current date at the top.
- A "To Do" filter is now added by default to the list view.
- The appraisal date color coding is refined. Dates are only displayed in red if they are before today and if the appraisal's state is neither Cancel nor Done.
- Both the final Interview and appraisal date columns in the list view will display dates in absolute terms instead relative dates.

Task-3777667

Swiss payroll functionality has been consolidated into the main Swiss payroll module, making related payroll and insurance reporting easier to maintain. Salary attachment handling was also moved into the core payroll area, improving consistency for payroll teams managing deductions and wage-related records.

The working schedules list now includes a Company Full Time column, which can help users compare schedules against the company standard. The column is hidden by default, so existing views remain uncluttered unless users choose to display it.

added company full time column on working schedules list view.
hidden by default

task-3954222

Website helpdesk forms now avoid adding the same customer-provided details twice when the ticket description already captures them. This keeps the ticket history clearer for support teams while preserving the information submitted by customers.

Before this commit, we got custom code to add custom message and add additional message to the description of the ticket.

This commit just log the message if the default field set on the website is the description field of the ticket field since now the description field will already contain the additional information gathered by the formulae filled by a public user.

task-3419255

Users handling Mexican electronic invoicing can now select the required payment method while creating or editing bank transactions in the bank reconciliation view. This helps businesses capture mandatory compliance information earlier in the accounting workflow and reduces follow-up corrections.

For Mexico, the payment way has to be declared.

This commit adds the ability to choose that value when creating/editing bank transactions in the bank reconciliation view.

Task [link](https://www.odoo.com/web#model=project.task&id=3874278)
task-3874278

The product configurator is now available on the website storefront for rental and subscription products, using the newer interface already adopted in the backend. It also keeps rental durations and subscription billing periods consistent between the main product and optional add-ons, making checkout choices clearer and less error-prone.

This change adapts the backend product configurator (which has been recently migrated to Owl [1])
to make it usable in the frontend as well, and uses it in the frontend.

This change also adds support for rentals and subscriptions in the product configurator, both in
the backend and the frontend (e.g. it displays the rental duration/billing period and ensures the
main and optional products use the same rental duration/billing period).

[1] https://github.com/odoo/odoo/pull/106511

Community PR: https://github.com/odoo/odoo/pull/153779
Upgrade PR: https://github.com/odoo/upgrade/pull/5896

task-3572125

Planning progress messages now more clearly explain whether an employee is unavailable because they are on leave or because their contract has expired. This helps managers understand scheduling issues faster and make better staffing decisions.

This PR enhances the accuracy of progress bar message because in the current flow the message was not clear about employee's status but now after this commit it is been clear either employee is on leave or its contract has been expired.

task-3609539

This update adjusts field service report testing and related views to reflect a newer rule that private tasks cannot have parent tasks. It helps keep the module compatible with recent project task validation changes and reduces the risk of test failures during upgrades.

This PR just adapt test to the constraint that has been added in related pr. Namely: "project_task_private_task_has_no_parent".

related: https://github.com/odoo/odoo/pull/131015
task-3450270

Odoo Studio now supports showing and editing documented widget options and attributes directly from the sidebar. This makes form customization more consistent and easier for users, while also tidying shared sidebar property components and improving subtitle sizing.

This commit is part of the improvements allowing to edit some widgets directly in the Sidebar, as well as fields were already available. Now, following commit (1), it is possible to add documentation to supportedOptions and attributes on widget components.

This is directly used to display the options accordingly in the Sidebar.

(1): https://github.com/odoo/odoo/commit/097f6c8709e4cbecf8d08e3683225b76fde97f8f

Spreadsheet pivots are now inserted using dynamic formulas instead of static grid content. This helps users refresh or adjust pivot data more safely and reduces unexpected errors caused by editing fixed pivot outputs.

This revision completely changes the insertion process of pivots inside
a spreadsheet. The pivots will now be inserted in the grid with their
dynamic formula. This will prevent people from editing static pivots and
getting errors out of the blue.

task-3947821

This update adds automated testing to verify that Balance Sheet reports are properly balanced across all localizations. The system now validates that debits equal credits in Balance Sheets by generating test transactions and checking the results, helping catch accounting errors early. This improvement ensures financial reports maintain their fundamental accounting principle of balanced entries.

This PR introduces a `l10n` test over the Balance Sheet reports.

Each Balance Sheet report in the `LOC_DATA` global at the head of the file will be tested.
The test generates a journal entry with a line in every account that is not `off_balance`.
It then checks whether the Balance Sheet is balanced.
The test does this both for debits and for credits.

The test will give a warning for any installed Balance Sheet report which is not specified in the LOC_DATA global. The aim is to change this to an error once all existing Balance Sheets are tested, to make this test mandatory for any new localizations.

For each localization with a Balance Sheet, the test needs to know the XMLIDs of:
- the CoA
- the Balance Sheet report
- the Total Assets line of the Balance Sheet
- the Total Liabilities line of the Balance Sheet
- the Total Equity line of the Balance Sheet (if applicable)

Setting the global `IDENTIFY_INCORRECT_ACCOUNTS` to `True` switches the behaviour of the test: it identifies the accounts that cause the imbalance using a binary search. This is off by default for runbot. 

**Performance impact**
- For each Balance Sheet, the test does the following:
     - load the chart template
     - create an account.move with 4 AMLs for each account (one debit and credit in the account; and one debit and credit in the counterpart account)
     - generate the report once.
- The Binary Search (which can be toggled when testing locally) is quite efficient: 
    - If there is just one incorrect account, then the report needs to be generated `log2(<number of accounts>)` times.
    - If there are `X` incorrect accounts, then in the worst-case the report may need to be generated `X * log2(<number of accounts>)` times.

On the Belgian CoA, with no incorrect accounts, the test takes 14s on my PC. With 4 incorrect accounts, the test takes 33s.

Task: 3060790

Forward-Port-Of: odoo/enterprise#36838

This update improves how Odoo handles global discounts and negative line items by moving the core logic to the main accounting module. This allows other countries' localization modules to reuse the same discount handling approach, while the Mexico localization module continues to provide country-specific tax and document processing. This change makes the system more efficient and easier to maintain across different regions.

To allow other localizations to use the same logic for negative lines, we moved the methods in account. 
We still extend it in the module to add specific logic about taxes and documents.

task-3943357