Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Moving issue type creating inconsistency in portfolio hierarchy

We have defined portfolio hierarchy as Initiative > Portfolio Epic > Capability > Epic > Story. While editing the Parent Link, JIRA will automatically show the right type when you are on an issue. This is the same in Portfolio Plan. This is good. 

However, one can change the Issue Type of an issue such that for example a Portfolio Epic can become a Capability. JIRA does no more than a warning message saying link is inconsistent with portfolio hierarchy and this is only visible in the issue. Now an Initiative is linked directly to a Capability as a result and this Capability is in turn linked to multiple Capabilities. Worst still, it no longer shows up in the Portfolio Plan because only Portfolio Epics will show up underneath Initiatives. 

In the meantime, our reporting, roll-up and automation fails because the hierarchy is wrong. 

Have you run into this? What do you do about it? We are very interested to hear any advice or suggestions please. Thank you!

1 comment

Same problem here ...


Just found your question... over 2 months no answers yet :(

Maybe I will try the normal support ... or we would have to report a bug


Log in or Sign up to comment