[MIG] operating_unit: Migration to 17.0

[jdidderen-nsi]

Compare to 16.0, I added a new method in the model "res.users". The method is inspired by the one on companies (https://github.com/odoo/odoo/blob/7266a662171fedc945523c5bc1bb34a4dd0995bf/odoo/api.py#L645) in the idea that at some point maybe a selector widget (like company one) will be added to choose the active OUs

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[AaronHForgeFlow]

Thank you for the migration and the refactor. Functional tests are good so far. Tested it using the migration of the account_operating_unit module for it. When the uneeded file is removed then I am fine with a merge.

[yankinmax]

@AaronHForgeFlow @gurneyalex
Can you pls help to get this merged?

[gurneyalex]

/ocabot merge nobump

[OCA-git-bot]

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 17.0-ocabot-merge-pr-667-by-gurneyalex-bump-nobump, awaiting test results.

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[OCA-git-bot]

Congratulations, your PR was merged at 549a3b0. Thanks a lot for contributing to OCA. ❤️

[jdidderen-nsi]

Just a quick message to thanks everyone for the help and the reviews on these modules.

FYI I will probably work on operating units during OCA days. For now, I have two improvements :

• Have a selector widget in the same approach as multi-company
• Improve report_qweb_operating_unit to have a different layout per operating unit (e.g having boxed in OU1 and stripped on OU2)