The IoT app now separates user presence handling from message notification handling. This internal cleanup makes the system easier to maintain and prepares it for future real-time communication improvements such as websockets.

The code handling user presence and the one handling bus notifications
are mixed up. In order to ease the PR introducing the websocket in Odoo
and to clear this mess, the presence service has been introduced.

task-2053917

community: https://github.com/odoo/odoo/pull/95981

The Documents app's main list and card-style views have been rebuilt on Odoo's newer web interface framework. This should make the app easier to maintain and better aligned with the rest of Odoo, while preserving the existing document management experience.

WIP

Due to some changes the route was not functioning properly anymore, as the 'context' arguments was directly parsed as the environment's context. This meant that the overrides that are done for `website_sale_renting` weren't working anymore making it impossible to add rental products with product configurator to the cart. Forward-Port-Of: odoo/enterprise#29551

Due to some changes the route was not functioning properly anymore, as
the 'context' arguments was directly parsed as the environment's
context.
This meant that the overrides that are done for `website_sale_renting`
weren't working anymore making it impossible to add rental products with
product configurator to the cart.

Forward-Port-Of: odoo/enterprise#29551

For the moment, there are no tree view for the Ticket Analysis model. Consequently, when accessing the view, we only see the ID of the models, which doesn't help the client. Step to reproduce the issue: 1. Install the Helpdesk module 2. Go to Reporting > Ticket Analysis > Cohort View (last small symbol on the top right) 3. Click on one of the entries to display the Ticket Analysis view You should see only a list of IDs. Solution: The Tree View related to the `helpdesk.ticket.report.

For the moment, there are no tree view for the Ticket Analysis model.
Consequently, when accessing the view, we only see the ID of the models, which
doesn't help the client.

Step to reproduce the issue:
1. Install the Helpdesk module
2. Go to Reporting > Ticket Analysis > Cohort View (last small symbol on the
top right)
3. Click on one of the entries to display the Ticket Analysis view
You should see only a list of IDs.

Solution: The Tree View related to the `helpdesk.ticket.report.analysis` did
not existed before. We had to create it.

opw-2839413

Forward-Port-Of: odoo/enterprise#26906

When generating the PDF for the SnailMail report, a script is executed to adapt the size of the address to match Pingen requirements (as per [1]). Step to reproduce the issue: 1) Have a contact created that has VAT configure 2) Create an invoice and 'Send and Print' 3) Select the POST button to send via POST 4) In dev mode, go to Techincal > Snailmail Letters 5) Download the PDF of the newly created invoice You should see that the font becomes extremely tiny. Solution: There are dif

When generating the PDF for the SnailMail report, a script is executed to
adapt the size of the address to match Pingen requirements (as per [1]).

Step to reproduce the issue:
1) Have a contact created that has VAT configure
2) Create an invoice and 'Send and Print'
3) Select the POST button to send via POST
4) In dev mode, go to Techincal > Snailmail Letters
5) Download the PDF of the newly created invoice
You should see that the font becomes extremely tiny.

Solution: There are different elements that needs to be corrected to solve the
issue.
1) The CSS used to specify the `height` requirement of the address was not
properly loaded (the path was incorrect)
2) The JS selector used into the resize script is incorrect
3) The CSS selector into the CSS file was invalid
All these issues are due to incomplete migrations.

[1]: https://github.com/odoo/odoo/commit/c50f5da4160c63dcc79900dc882cd36c9ad96b2e

opw-2819823

Forward-Port-Of: odoo/enterprise#28663
Forward-Port-Of: odoo/enterprise#27712

Prior to this commit if a journal to synchronize was configured in the document_account settings was setup it would always override the tags regardless of prior state. This means that for documents created by workflow actions the tags would simply not work properly for example with the action "Create Bill". OPW-2909133 Forward-Port-Of: odoo/enterprise#29497 Forward-Port-Of: odoo/enterprise#29422

Prior to this commit if a journal to synchronize was configured in the
document_account settings was setup it would always override the tags
regardless of prior state.
This means that for documents created by workflow actions the tags would
simply not work properly for example with the action "Create Bill".

OPW-2909133

Forward-Port-Of: odoo/enterprise#29497
Forward-Port-Of: odoo/enterprise#29422