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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,467,272
Community Members
 
Community Events
177
Community Groups

Custom Hierarchy in JIRA Portfolio

It appears that in a recent update, the hierarchy link between a custom level (parent to Epic) lost linkage to the child level. Can anybody tell me what might have happened? We have hundreds of issues that now need to be re-linked.

3 answers

Support came through - dead simple though not terribly intuitive:

That Story issue type that is currently on top of the Epic was manually added since you can see the "Remove" link in the "Actions" column.
To make the Story issue type below the Epic again you would need to remove the manual entry (by clicking the Remove link) and the Story issue type will be below it since it will be encompass by the "All other standard issue types" option, which is the default hierarchy as explained here Configuring initiatives and other hierarchy levels.

I think I am having the same issue. Any help out there?

I too facing same issue, Unable to move/configure, EPIC->Story...Something was changed recently.

Atlassian support tracked down the problem - for the custom issue type we created, we did not need "Fix Version" - however, Portfolio requires this field on the issue. Once Fix Version was added back to the custom issue, everything worked fine once again.

Thanks, Jenine. I'm not actually using a custom issue type, so I was mistaken. I think my issue may not be exactly the same, but still seems somewhat related... hopefull Atlassian support can help me too!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events