[17.0][MIG] project_tag_hierarchy: migration to version 17.0 #1648
+766
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently translated at 100.0% (5 of 5 strings) Translation: project-16.0/project-16.0-project_tag_hierarchy Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_tag_hierarchy/it/
atgalvez08
force-pushed
the
17.0-mig-project_tag_hierarchy
branch
from
69ca86e to
076cf5b
Compare
Contributor
|
/ocabot migration project_tag_hierarchy |
leemannd
approved these changes
Jan 13, 2026
|
@rrebollo @antoniodavid would you guys review this please ? |
Contributor
|
This PR has the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@BinhexTeam
This PR migrates the addon
project_tag_hierarchyto Odoo 17.0 usingoca-port, preserving the original addon history.Main changes introduced during the migration:
name_getoverride with a computeddisplay_namefield using_compute_display_name, following Odoo 17 core guidelines.parent_id, as Odoo 17 already enforces recursion detection at core level for models using_parent_store, raising aUserErrorbefore model constraints are evaluated.TransactionCaseand proper test tagging).Fixes #1191