The helpdesk live chat tests now use the actual parent discussion component instead of a custom test helper. This makes test coverage closer to real user behavior and helps reduce future maintenance risk.

Use real parent instead (Discuss in this case).

Timesheet overtime is now calculated using the employee contract that was active on the date of the timesheet, rather than the employee's current contract. This improves payroll and reporting accuracy when employees change contracts, schedules, or working hours over time.

Allows the timesheet overtime computation to be based on the contract
the employee had on the day of the timesheet instead of his current
contract.

TaskID-2652259

This update adapts accounting, tax, sales, appointment, and follow-up features to a newer internal data-handling API. It should improve long-term maintainability and consistency without changing day-to-day user workflows.

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

This change simplifies how several kanban screens trigger actions across manufacturing, signing, and barcode workflows. It reduces custom code behind the scenes, making these views more reliable and easier to modernize without changing day-to-day user behavior.

This PR uses the new 'action'/'type' attributes on kanban view to simplify various kanban record .includes.

In Settings>Accounting>[Vendor Payments] Checks select 'Print Check (bottom) - US" Create a vendor payment of type check, input amount and vendor. Confirm and print the check A last blank page is present This occur because the css class `.ckus_check` has the attribute 'height' defined in `report_check_bottom.scss` and overridden in `report_check_bottom.scss`. The override was working thanks to the file order, which before d9bdcbc6d34fce1149bd216bdd6dbad964947fa9 was defined as - re

In Settings>Accounting>[Vendor Payments] Checks select 'Print Check
(bottom) - US"
Create a vendor payment of type check, input amount and vendor. Confirm
and print the check

A last blank page is present

This occur because the css class `.ckus_check` has the attribute
'height' defined in `report_check_bottom.scss` and overridden in
`report_check_bottom.scss`.
The override was working thanks to the file order, which before
d9bdcbc6d34fce1149bd216bdd6dbad964947fa9 was defined as
- report_check_common.scss
- report_check_bottom.scss
Now we use the glob pattern 'l10n_us_check_printing/static/**/*',
the correct order is lost and the common height will be applied.

opw-2838272

Forward-Port-Of: odoo/enterprise#27111

Step to reproduce: -install payslip -set on an employee contract a wage with decimal value -set attendance for this employee (if he did not already have some) -create a payslip for this employee with the modified contract Current behavior: The wage in the "worked days & inputs" and "salary computation" does not have the decimal values of the contract wage (00 instead) Expected behavior: The wage in the "worked days & inputs" and "salary computation" have the decimal values of t

Step to reproduce:
	-install payslip
	-set on an employee contract a wage with decimal value
	-set attendance for this employee (if he did not already have some)
	-create a payslip for this employee with the modified contract

Current behavior:
The wage in the "worked days & inputs" and "salary computation" does not
have the decimal values of the contract wage (00 instead)

Expected behavior:
The wage in the "worked days & inputs" and "salary computation" have the
decimal values of the contract wage

Explanation
The worked_days had their amount computed based on the deprecated
normal_wage value of the payslip that is an integer and does not
take into account the decimals of the contract_wage. To solve the
issue we replace the normal_wage with the contract_wage

https://github.com/odoo/enterprise/blob/929d43e815437c58f15b122e20f56a62c1280326/hr_payroll/models/hr_payslip.py#L110-L111

opw-2845145

Forward-Port-Of: odoo/enterprise#27710
Forward-Port-Of: odoo/enterprise#27175

Before merging subscription with sale orders, when a quotation of a subscription product was paid in portal, the payment token was already saved to the subscription automatically. After merging subscription and sale, this behavior was lost. This commit introduces the code to properly save the payment token into the subscription if the payment mode is set to 'success_payment'. task-2824236 Forward-Port-Of: odoo/enterprise#26235

Before merging subscription with sale orders, when a quotation of a
subscription product was paid in portal, the payment token was already saved to
the subscription automatically. After merging subscription and sale, this
behavior was lost. This commit introduces the code to properly save the payment
token into the subscription if the payment mode is set to 'success_payment'.

task-2824236

Forward-Port-Of: odoo/enterprise#26235

Currently in the payroll app there is a boolean field responsible for showing hr.salary.rules in the employer cost dashboard plot. However, some rules are always shown, as they are hard-coded. This commit fixes this behavior by using the boolean field to show these rules, therefore giving more flexibility to the plots as we are able to hide the previous hard-coded rules. task-2836922 Forward-Port-Of: odoo/enterprise#27065

Currently in the payroll app there is a boolean field responsible for showing
hr.salary.rules in the employer cost dashboard plot. However, some rules are
always shown, as they are hard-coded. This commit fixes this behavior by using
the boolean field to show these rules, therefore giving more flexibility to the
plots as we are able to hide the previous hard-coded rules.

task-2836922

Forward-Port-Of: odoo/enterprise#27065

The `name` of a `res.partner` isn't a required field, this caused a traceback when calling `lower()` on an undefined name. Forward-Port-Of: odoo/enterprise#27724

The `name` of a `res.partner` isn't a required field, this caused
a traceback when calling `lower()` on an undefined name.

Forward-Port-Of: odoo/enterprise#27724

The gray lines are not appearing on the total column in timesheet because of the background color applied on the total column This commit fixes the issue by removing the background color from the total column, so that the gray line is always visible on the total column taskID: 2774812 Forward-Port-Of: odoo/enterprise#25685

The gray lines are not appearing on the total column in timesheet
because of the background color applied on the total column

This commit fixes the issue by removing the background color from
the total column, so that the gray line is always visible on the total column

taskID: 2774812

Forward-Port-Of: odoo/enterprise#25685