[19.0][MIG] agreement: Migration to 19.0#99
Conversation
we move the is_template field definition and the agreement.type model from the agreement_legal module to the agreement module. The fields are not displayed by default, unless the feature is enabled through a technical feature group, this is configurable in the agreement_sale module (because agreement in itself has no UI, and agreement_legal enables the feature by default)
- The `agreement` model now features mail and activities from its base module. - The `agreement_legal` module doesn't need to add mail support now. - Add activities to form views. @Tecnativa TT22477
Update agreement and agreement_sale to restore the behavior of v10
…ad of onchange field
Co-authored-by: Denis Roussel (ACSONE) <rousseldenis@users.noreply.github.com>
6540d3e to
6f1b2e5
Compare
|
/ocabot migration agreement |
|
Hello @Vang-NguyenPhu , Is it possible to reduce the commit history by following -> https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-19.0
|
6f1b2e5 to
8f1b55a
Compare
|
|
Currently agreement and agreement_legal is a little confusing. Especially the Form, which is in agreement_legal not reused. Maybe we can change agreement a little bit so that the extensions can more easily link in?
In agreement_legal there is already a roadmap what should be changed. We are not yet using agreement but are interested. Currently there is a lot of stuff we don't need and would like to hide (or better not install). cc: @MohamedOsman7 |
CRogos
left a comment
There was a problem hiding this comment.
Could you squash some of the commits?
|
Hello @OCA/project-service-maintainers can you pls take a look and possibly trigger merge? |
Currently translated at 100.0% (64 of 64 strings) Translation: agreement-17.0/agreement-17.0-agreement Translate-URL: https://translation.odoo-community.org/projects/agreement-17-0/agreement-17-0-agreement/it/
Currently translated at 100.0% (72 of 72 strings) Translation: agreement-18.0/agreement-18.0-agreement Translate-URL: https://translation.odoo-community.org/projects/agreement-18-0/agreement-18-0-agreement/it/
By shifting the constraint to the commercial entity, computed from the partner field, we can now select hierarchy contacts. This is useful to: A) Register the contact person of the agreement B) Support modules like `partner_affiliate`, in case of nested businesses
Currently translated at 100.0% (72 of 72 strings) Translation: agreement-18.0/agreement-18.0-agreement Translate-URL: https://translation.odoo-community.org/projects/agreement-18-0/agreement-18-0-agreement/de/
Currently translated at 100.0% (72 of 72 strings) Translation: agreement-18.0/agreement-18.0-agreement Translate-URL: https://translation.odoo-community.org/projects/agreement-18-0/agreement-18-0-agreement/fr/
Currently translated at 100.0% (72 of 72 strings) Translation: agreement-18.0/agreement-18.0-agreement Translate-URL: https://translation.odoo-community.org/projects/agreement-18-0/agreement-18-0-agreement/sv/
Currently translated at 100.0% (74 of 74 strings) Translation: agreement-18.0/agreement-18.0-agreement Translate-URL: https://translation.odoo-community.org/projects/agreement-18-0/agreement-18-0-agreement/it/
Currently translated at 100.0% (74 of 74 strings) Translation: agreement-18.0/agreement-18.0-agreement Translate-URL: https://translation.odoo-community.org/projects/agreement-18-0/agreement-18-0-agreement/sv/
Currently translated at 100.0% (73 of 73 strings) Translation: agreement-18.0/agreement-18.0-agreement Translate-URL: https://translation.odoo-community.org/projects/agreement-18-0/agreement-18-0-agreement/it/
8f1b55a to
5f522f7
Compare
I think it's good now. |
|
Hello @rousseldenis , sorry for pinging you directly, can you pls take a look and possibly trigger merge? |
|
/ocabot merge nobump |
|
What a great day to merge this nice PR. Let's do it! |
|
Congratulations, your PR was merged at 63e3618. Thanks a lot for contributing to OCA. ❤️ |

No description provided.