This update brings online quotation and payment capabilities more directly into the Sales app, simplifying the sales workflow. It also refreshes the customer portal experience for quotations, signatures, breadcrumbs, and order actions, making it easier for customers to review and accept quotes.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

This update refreshes the customer-facing online quotation experience so sales orders look and behave more like modern website quotes. It improves mobile usability, adds clearer navigation and document history access, and fixes related portal issues such as signature layout and portal access errors.

Description of the issue/feature this PR addresses:
Task ID: https://www.odoo.com/web?#id=49205&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720

Current behavior before PR:

Desired behavior after PR is merged:




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

This update brings quotation and online payment features directly into the main Sales apps, making them available without extra website-related modules. Customers get a clearer sales order portal with signing, payment, optional products, and quotation template improvements, while administrators gain new settings to control these features.

Tasks:
https://www.odoo.com/web#id=49205&action=333&active_id=967&model=project.task&view_type=form&menu_id=4720
and
https://www.odoo.com/web#id=1838924&action=333&active_id=1217&model=project.task&view_type=form&menu_id=4720

This change keeps existing timesheets tied to the original project, sales order line, and analytic account when a task is moved or rebilled, protecting past billing records from unintended changes. It also improves billable project setup by supporting employee-specific billing rates, clearer project billing settings, subtask sales line handling, and easier access to project configuration.

https://www.odoo.com/web?debug#id=34703&action=333&active_id=965&model=project.task&view_type=form&menu_id=4720



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

Manufacturing can now better handle components coming from multiple stock locations by automatically setting up the needed warehouse routes, locations, and transfers. This helps businesses coordinate materials before production, manage related sales, purchase, and manufacturing documents more safely, and notify users when manual follow-up is needed after quantity reductions or cancellations.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Users can now see when someone is typing in direct messages, channels, and livechat conversations, making real-time conversations feel more responsive. The update also includes several fixes and cleanup in the mail and livechat areas to improve message previews, unread counts, window behavior, styling, and livechat reliability.

Task "is typing..." notification on channels, DMs and Livechats (see task ID 28188)

Note that document threads and mailboxes (obviously) do not have this feature active. For the livechat, this feature is bidirectional: the operators sees when the website client is typing, and vice versa..

Some technical details:

- Notify start/stop mechanism, instead of regularly notify is typing.
- Can only notify once per 2.5 seconds to the server that we start or stop typing (throttled behaviour).
    - Clearing composer => notify stop typing
    - Sending message => receiver detects message received from someone that is typing => know that he is no longer typing something
- When the user does not input anything for 5 seconds, it automatically notifies that he is no longer typing anything (soft timeout - cooperative sender).
- Receivers do not receive a typing notification after 60 seconds, they assume the person stopped typing something (hard timeout - receiver assumption).
- If typing partners are currently typing for more than 50 seconds straight, they notify that they are still typing something (again and again every 50 seconds).
- When there are several users typing at the same time, it displays at most 2 users that are currently typing something.

As a result:
- Usually 2.5 seconds uncertainty.
- Up to 5.0 seconds on typer inactivity.
- Up to 60 seconds if typer reloads page / browser crashes / etc.


Task ID: 28188