Following the fix done in #50763, this changes achieves a better behavior of the fix, where we make a better calculation to know when we should rotate the text when we don't have space to display it horizontally. Forward-Port-Of: odoo/enterprise#56151

Following the fix done in #50763, this changes achieves a better behavior of the fix, where we make a better calculation to know when we should rotate the text when we don't have space to display it horizontally.

Forward-Port-Of: odoo/enterprise#56151

The aim of this commit is making sure that we only have inbound moves in `Dispatch` category and outbound moves in `Arrival` category. no task id Forward-Port-Of: odoo/enterprise#56887 Forward-Port-Of: odoo/enterprise#56747

The aim of this commit is making sure that we only have inbound moves in `Dispatch` category and outbound moves in `Arrival` category.

no task id

Forward-Port-Of: odoo/enterprise#56887
Forward-Port-Of: odoo/enterprise#56747

IAP: https://github.com/odoo/iap-apps/pull/751 Documentation: https://github.com/odoo/documentation/pull/7683 task-id 3704792 Forward-Port-Of: odoo/enterprise#55858

IAP: https://github.com/odoo/iap-apps/pull/751
Documentation: https://github.com/odoo/documentation/pull/7683

task-id 3704792

Forward-Port-Of: odoo/enterprise#55858

The aim of this commit was originally adding a test to verify that we could unfold the report. After some investigations, we discovered that we have several fields in `account_intrastat` that are using `one2many` fields in related fields (causing an issue in our test). Thus, this commit is changing related fields to computed one. We decided arbitrary that we'll take the first value of the `one2many` field for each computed ones. no task id Forward-Port-Of: odoo/enterprise#56699 Forward-

The aim of this commit was originally adding a test to verify that we could unfold the report.

After some investigations, we discovered that we have several fields in `account_intrastat` that are using `one2many` fields in related fields (causing an issue in our test).
Thus, this commit is changing related fields to computed one.
We decided arbitrary that we'll take the first value of the `one2many` field for each computed ones.

no task id

Forward-Port-Of: odoo/enterprise#56699
Forward-Port-Of: odoo/enterprise#56525

https://github.com/odoo/enterprise/pull/31893 wrongly removed views in stable versions. Problems: 1. The version on the folder is wrong: 16.0.1.1 will only be executed in 16.0 while the change has been done in all versions (the folder name should've been 1.1). 2. The script is using upgrade-util. This cause a traceback when trying to update the module. No local script in standard can ever assume that upgrade-util is available. There is no dependency between odoo and the utils for now, it m

https://github.com/odoo/enterprise/pull/31893 wrongly removed views in stable
versions. Problems:
1. The version on the folder is wrong: 16.0.1.1 will only be executed in 16.0
while the change has been done in all versions (the folder name should've been 1.1).
2. The script is using upgrade-util. This cause a traceback when trying to update the module.
No local script in standard can ever assume that upgrade-util is available.
There is no dependency between odoo and the utils for now, it might come at some
point but we are far from here.
3. Removing views in stable is against stable policy.

To fix this:
1. We remove the wrong script from odoo repository. The records *should* be deleted
correctly by the ORM. It may fail if a customization is using the templates.
2. Add an upgrade script that will remove the views on major versions, in case the ORM failed
to remove them by itself.

opw-3741655
See https://github.com/odoo/upgrade/pull/5698

Forward-Port-Of: odoo/enterprise#56698