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.
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.
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.
We've just launched a brand new guide to help you get started with Portfolio for Jira. This guide is a companion piece to our new demo. The guide walks you through use-cases, best practices an...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG