Conversation
7e239bf to
e09aa87
Compare
|
@newtratip please check out this PR #397 |
|
Sorry the PR is this #578 |
|
@sergio-teruel, I saw this PR #578 not plan to work anymore and then it will closed. Should I check out on this one or waiting another PR supersede #578 My question : agreement is changed to base_contract, it's ok. and I am migrating agreement_legal module. Should this module still be name Thanks ! |
|
Hi @newtratip I not sure... I asked Alexis about PR (#578) (#578 (comment)) status... and he will not continue working on it, so I'm thinking... Why do we go to change the name...??? |
|
This PR has the |
e09aa87 to
c2cc8fd
Compare
|
Thanks @newtratip |
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
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: contract-12.0/contract-12.0-agreement Translate-URL: https://translation.odoo-community.org/projects/contract-12-0/contract-12-0-agreement/
Update agreement and agreement_sale to restore the behavior of v10
7dac775 to
b4eeb47
Compare
b4eeb47 to
8c16c94
Compare
|
Additional update, I check out this PR #628 |
|
/ocabot merge nobump |
|
On my way to merge this fine PR! |
|
Congratulations, your PR was merged at d41be91. Thanks a lot for contributing to OCA. ❤️ |
Standard Migration