You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
we have been actively using Portfolio for over 2 years. Currently we have hierarchy as Initivative -> Feature -> Epic. Some of teams want to add "Theme" as a new Issuetype and at the top level of hierarchy. Will this impact any functionality of the other users who do not want to see this change. I know hierarchy for portfolio is global and cannot be set on project level. Please advice.
It shouldn't be an issue if added to the top of the hierarchy.
It's true that all plans will now have Theme in them - although users can choose to view from Initiative downwards, meaning for those who don't want Theme this should have minimal impact.
From an issue perspective - it would mean users could relate their Initiatives to any created Theme via the Parent Link. You could check compliance here through issue searches.
If you want to discourage creation of them in projects who do not see a need for them, you could just add Theme to projects' Issue Type Schemes who want them, meaning certain projects would not have the option to create them?
The hierarchies are global and the issue types will be mapped to it will be reflected in all the plans using it.