Durations are now shown in days when that is the selected tracking unit, instead of being displayed as hours. This removes confusing inconsistencies across helpdesk, field service, timesheet forecasting, and related reports, making planning and reporting easier to understand.

The purpose of this task is there are several places where the
duration is expressed in hours even though the encoding unit
is in Days. This creates inconsistencies.

In this commit, we convert hours into days when the encoding
unit is in Days. Also, we changed the string of the fields
according to the encoding unit.

Task-Id: 2512950
PR: #18197

Deleting a sales team now has an explicit, predictable effect on subscription records: the team link is cleared instead of leaving uncertainty. Subscription history remains trackable where it contains useful sales information, helping users preserve context while allowing old teams to be removed safely.

SET NULL

  * sale.subscription: void team_id field but track it as it holds sales
    information people may want to keep as history (no change);
  * sale.subscription.log: void team_id field (no change);

The customer follow-up screen now correctly shows the formatted success message after completing an action. This keeps the confirmation experience clear and consistent for users following up on unpaid invoices.

This commit adds option messageIsHtml: true because now
that message of rainbowman is escaped by default we need to
mark it as html

task-id: 2575435

The navigation bar now still shows the home menu button when the first loaded action fails, such as after refreshing the page. This helps users recover and continue navigating instead of being stuck without an obvious way back.

… action

Have an initial action (with F5) that will fail.

Before this commit, the navbar's button to display the home menu was not visible.

After this commit, its is visible

Odoo Studio was adjusted to work with a simplified internal action flow. This keeps Studio menus and navigation compatible with platform changes without changing the user experience.

The Gantt view internals were reorganized to make Planning and Project customizations easier to maintain. This reduces technical complexity behind row naming and grouping, supporting future improvements with minimal direct user impact.

This reverts commit a90916abcfa61b4b4f250d27b27421eef1aa4f49. We don't care about the most recent rates; the report should only use values in the company currency as the total of the aged reports needs to be equal to the total of the general ledger. opw-2545125 Forward-Port-Of: odoo/enterprise#19196 Forward-Port-Of: odoo/enterprise#19096

This reverts commit a90916abcfa61b4b4f250d27b27421eef1aa4f49.

We don't care about the most recent rates; the report should only use
values in the company currency as the total of the aged reports needs to
be equal to the total of the general ledger.

opw-2545125

Forward-Port-Of: odoo/enterprise#19196
Forward-Port-Of: odoo/enterprise#19096

Forward-Port-Of: odoo/enterprise#19186

Forward-Port-Of: odoo/enterprise#19186

On mobile/smaller screens, in the Form view, once there is more than one button in the statusbar, they are grouped into a dropdown to prevent from cluttering/breaking the layout due to the restricted available space. In the first implementation of this feature, those buttons were merged into a dropdown no matter how many buttons were present. The drawback was that if only one button was present, the dropdown introduced an unnecessary click/touch in the flow. A second iteration of this

On mobile/smaller screens, in the Form view, once there is more than one
button in the statusbar, they are grouped into a dropdown to prevent
from cluttering/breaking the layout due to the restricted available
space.

In the first implementation of this feature, those buttons were merged
into a dropdown no matter how many buttons were present. The drawback
was that if only one button was present, the dropdown introduced an
unnecessary click/touch in the flow. A second iteration of this
implementation introduced the current conditional grouping... but also
added some complexity as every modifier (ie. invisible) could change de
number of buttons displayed, and in consequence, the need to group them
into a dropdown.

We discovered during the execution of the main flow tour on powerful
enough hardware (like the runbot) that some timing conjunction between
the actions performed in the UI and the responses of the server could
lead to an unexpected state of the dropdown.

More precisely:
- When the main flow tour mobile reaches the Vendor Bill creation step
- The newly created bill is edited to set the invoice_date
- This edit triggers both an 'onchange' and recompute the 'modifiers'
- Every application of the modifiers rerender the dropdown (if needed)
- But the 'onchange' response can also influence the modifiers
- If the dropdown is opened before the 'onchange' response, it will be
closed again once the onchange's triggers a rerender of the dropdown.
This case is less likely to happen due to a 'real user' interaction time
but may occur via the automation of the tours.

This commit fixes it by keeping the state (open/close) of the dropdown
at the FormRenderer's level to avoid this kind of timing issue and
prevent dropdown's flickering.

Forward-Port-Of: odoo/enterprise#19170
Forward-Port-Of: odoo/enterprise#19099