The manufacturing work order tests were adjusted to reflect support for manual material consumption. This helps ensure the feature behaves reliably as manufacturing processes are validated, with no direct change expected for everyday users.

Adapt tests to support manual consumption in Mrp.

Task-2687494

This update standardizes how links are created inside record discussions across several business apps. It helps keep messages and cross-references consistent, making it easier for users to navigate between related documents such as invoices, tasks, repairs, payroll items, subscriptions, and helpdesk records.

Community PR: https://github.com/odoo/odoo/pull/84866

The Helpdesk screens were refreshed to rely more on standard layout building blocks and less on custom styling. This makes the interface more consistent, fixes small display issues including Safari table sizing, and improves readability on smaller screens.

This PR simplifies the SCSS and reorganizes the Bootstrap classes in the XML to use as little raw SCSS as possible. It also improves minor layout issues.


task-2754091

Odoo Enterprise modules were updated to match a backend reorganization of web controller files. This keeps existing features working with the new structure and has little direct impact on daily users.

The odoo.addons.web.controllers.main python module have been splitted
over multiple files on the basis 1 controller = 1 file. In this work we
adapt all modules to use the new imports.

A non-exhaustive list of where stuff have been moved:

* main.Home             --> home.Home
* main.Session          --> session.Session
* main.WebClient        --> webclient.WebClient
* main.clean_action     --> action.clean_action
* main.ensure_db        --> home.ensure_db

The complete list is accessible in odoo.addons.web.controllers.main.

Companion of odoo/odoo#87571

The Planning shift window now shows its action buttons with proper spacing. This makes the interface easier to read and reduces the chance of users clicking the wrong button.

…ave a space

Before this commit, In planning_view_form_in_gantt, buttons did not have padding

This commit fixes the issue by adding a padding to the button

task-2792884

This update removes obsolete code from several accounting-related modules that was no longer being used. It helps keep the system easier to maintain without changing day-to-day business workflows.

Before this commit it was not possible to change/extend the domain for subscriptions to invoice. By adding it in a separate function, we can do a clean extend of the domain. -- I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr) Forward-Port-Of: odoo/enterprise#25757 Forward-Port-Of: odoo/enterprise#25563

Before this commit it was not possible to change/extend the domain for subscriptions to invoice.
By adding it in a separate function, we can do a clean extend of the domain.

--
I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr)

Forward-Port-Of: odoo/enterprise#25757
Forward-Port-Of: odoo/enterprise#25563

File was not deleted in forward ports of commit https://github.com/odoo/enterprise/pull/24029/commits/499a95c33f336506b1fe9dd143715ed3c1344cfc Task: 2752565 Forward-Port-Of: odoo/enterprise#25653 Forward-Port-Of: odoo/enterprise#25153

File was not deleted in forward ports of commit https://github.com/odoo/enterprise/pull/24029/commits/499a95c33f336506b1fe9dd143715ed3c1344cfc

Task: 2752565

Forward-Port-Of: odoo/enterprise#25653
Forward-Port-Of: odoo/enterprise#25153

A user can't be available in the past, so the slots shouldn't be counted as available. Forward-Port-Of: odoo/enterprise#24008

A user can't be available in the past, so the slots shouldn't be
counted as available.

Forward-Port-Of: odoo/enterprise#24008

Forward-Port-Of: odoo/enterprise#25502

Forward-Port-Of: odoo/enterprise#25502

Steps to reproduce the bug: - Create a storable Product “P1”: - Add a BOM with component: - “C1”, $50 of cost, 1unit needed - “C2” $20 of cost, 1 unit needed 1:/ - Create a MO: - select p1 with 10unit to produce - Confirm and validate 2:/ - Change the cost of “C1” to $30 - Create a second “MO”: - Select P1 with 20 units to produce - Go to MRP > Reporting > Production analysis there is a pivot table with different measures. Problem: All avera

Steps to reproduce the bug:
- Create a storable Product “P1”:
   - Add a BOM with component:
        - “C1”,  $50 of cost, 1unit needed
        - “C2” $20 of cost, 1 unit needed

1:/
- Create a MO:
    - select p1 with 10unit to produce
    - Confirm and validate

2:/
- Change the cost of “C1” to $30
- Create a second “MO”:
    - Select P1 with 20 units to produce

- Go to MRP > Reporting > Production analysis there is a pivot table with different measures.

Problem:
All average cost measurements are incorrect, for example, the current AVG/unit cost calculation is:

((50 + 20) + (30 + 20)) / 2 Nb production = 60

The average should take into account the quantities produced in each MO,
and not simply the number of manufacturing orders. So the correct calculation:
(((50+20)*10) + ((30 + 20)*20)) / (20 + 10) = 56.67

The SQL query is correct, it is when applying the read_group that the calculation is incorrect,
we should override it to make a personalized calculation of the average

opw-2767504

Forward-Port-Of: odoo/enterprise#25676
Forward-Port-Of: odoo/enterprise#25594