Payment links generated from subscriptions now give customers clearer context about what they are paying for, instead of showing only a reference and amount. This reduces confusion during payment and can help customers complete subscription payments with more confidence.

If user generated payment link, it was very unclear, client had no idea what is he actually paying for, they only had reference and amount.

See also:
 - https://github.com/odoo/odoo/pull/162177

The salary attachment report has been removed because the same information is now available directly in the salary attachment view. A new pivot view lets payroll users analyze salary attachment data in a more flexible way without relying on a separate report.

The salary attachment report was kind of pointless since we can get the same info in the salary attachment view. Added a pivot view for salary attachment to get a similar report to the one existing previously.

Task: 3960990

Employee-related action menus have been simplified by moving or removing less-used options. This makes employee list and form screens easier to read and helps users find key actions in more appropriate places.

This Pr unclog the different hr action menu an move functionnalities in a more appropriate place to be more user firendly


task-3927336


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

The Sign template action previously called Duplicate has been moved to a more appropriate place and renamed Edit. This makes the action clearer for users when they need to modify or reuse signing templates.

In the Sign module, move the 'Duplicate' button to a new location and rename it to 'Edit'.

task: 3977796

Payroll users can now delete a batch when it has no payslips or when all linked payslips are still draft or canceled. This reduces cleanup friction while keeping completed or active payroll records protected.

This PR improves the batch deletion process in the hr_payroll module. Users can now delete a batch if all payslips within it are in a canceled or draft state, or if no payslips are linked to the batch.

task-3964984

This update improves wording, labels, placeholders, filters, and navigation across appointment scheduling, WhatsApp templates, social posting, and marketing automation. These refinements make common screens clearer and easier to use, while also updating demo social links so examples point to valid official content.

Batch of small improvements like labels, design, ...
See commits for more details.

task-3515819

This change simplifies the internal tour testing setup by moving disabled-element checks from each tour step definition into the shared action helpers. It keeps test behavior consistent while reducing maintenance across business apps such as Approvals, Payroll, Planning, Studio, Inventory, Rentals, and Appointments.

To simplify the tours API and the number of keys a tour step can have, it was decided to remove the allowDisabled key.
In reality, it was not really removed but moved to the tour helpers side.
Indeed, when performing the action, we check at that moment whether the targeted element is enabled or not depending on the action that is performed (click, dblclick, draganddrop,...). If the element isn't enabled, it throws an error.

task~3974087

https://github.com/odoo/odoo/pull/171028

This update improves the report editor in Odoo Studio by aligning it with the newer editing framework and correcting minor naming mistakes. It also makes report editing more efficient when handling document content, supporting smoother maintenance and future enhancements.

In this PR: Steps to reproduce: 1. Create a POS session. 2. Make two orders: one with an invoice and one without. Close the session. 3. Create another session, make an order, and create an invoice for an order from the previous session. Close the session. 4. Create a GST return period and generate the GSTR-1 spreadsheet. Changes made: - Fixed the retrieval of POS line details by move ID. - Added a safe access method using get to prevent key errors during HSN summary generation. Ta

In this PR:

Steps to reproduce:
1. Create a POS session.
2. Make two orders: one with an invoice and one without. Close the session.
3. Create another session, make an order, and create an invoice for an order from the previous session. Close the session.
4. Create a GST return period and generate the GSTR-1 spreadsheet.

Changes made:
- Fixed the retrieval of POS line details by move ID.
- Added a safe access method using get to prevent key errors during HSN summary generation.

Task ID: 3935317

Forward-Port-Of: odoo/enterprise#66596
Forward-Port-Of: odoo/enterprise#66311

Forward-Port-Of: odoo/enterprise#66635

Forward-Port-Of: odoo/enterprise#66635

**Steps to reproduce the bug:** - Create a storable product P1 with BoM: - Component: Add any component - operation: OP1 - Create a MO with P1: - Confirm it - Start the workorder and mark it as done - Come back to the dashboard > workorders list - Select the finished workorder - Try to start it **Problem:** The work order can be started while it is in the 'done' state. When the function `button_start` is called, we will check if we need to skip the employee ch

**Steps to reproduce the bug:**
- Create a storable product P1 with BoM:
    - Component: Add any component
    - operation: OP1

- Create a MO with P1:
    - Confirm it
    - Start the workorder and mark it as done
- Come back to the dashboard >  workorders list
- Select the finished workorder
- Try to start it

**Problem:**
The work order can be started while it is in the 'done' state.

When the function `button_start` is called, we will check if we need to
skip the employee check or not. However, since the current user is also
an employee, we will use them:
https://github.com/odoo/enterprise/blob/c4604d8b398713898b014e6073219d6202c154c3/mrp_workorder/models/mrp_workorder.py#L258-L259
The function start_employee will then be called:
https://github.com/odoo/enterprise/blob/c4604d8b398713898b014e6073219d6202c154c3/mrp_workorder/models/mrp_workorder.py#L284-L286
The state of the work order will then be updated:
https://github.com/odoo/enterprise/blob/c4604d8b398713898b014e6073219d6202c154c3/mrp_workorder/models/mrp_workorder.py#L740"

opw-4024904

Forward-Port-Of: odoo/enterprise#66358

task-4004305 Forward-Port-Of: odoo/enterprise#65167

task-4004305

Forward-Port-Of: odoo/enterprise#65167

Updated description when connecting new IoT Box to db, added help buttons redirecting to Odoo documentation. Task: 4021957 Forward-Port-Of: odoo/enterprise#66298

Updated description when connecting new IoT Box to db, added help buttons redirecting to Odoo documentation.

Task: 4021957

Forward-Port-Of: odoo/enterprise#66298