I have upgraded to Jira Software Cloud Premium in order to access Advanced Roadmaps and Hierarchy organisation. I need to add another hierarchy (called "Initiative") and have followed the steps by adding the initiative issue type to my board and have also added it at the Level 1 heirachy level above Epic in the Hierarchy organization screen. However, when I go to create a new Initiative issue in my Classic Kanban board, it doesn't show at a level above the EIC level, instead it gives me the same level as Story or Task.
Would appreciate the community's thoughts on what I am missing or doing wrong.
Thanks very much
Aside from Sub-Tasks, all issues are classed as standard issue types - including Epic.
The Epic utilises a special relationship using the "Epic Link" field to become a parent of stories and tasks.
Initiatives (or any issue type) in the Advanced Roadmap hierarchy does something similar - you need to ensure you add the Parent Link field to the screen that Epics use. This will allow you to set the Epic as a child of the Initiative!
Just to note this doesn't effect how a board works - so there isn't an Initiative Panel or similar. If Initiatives are appearing on your board and you don't want them to, you'll need to modify the Board Filter to exclude this issue type.
Let us know if this answers your query - or if you need any specific instructions for adding Parent Link field or similar :)
Hi Stephen, thank you for your response, it is really helpful and now I better understand how the hierarchies work in Jira. Could you please point me in the right direction for the instructions on how to add the Parent Link in an Epic issue. Thanks and Kind Regards, Carolyn
To add the Parent Link to the Epic's screen, this is how to do it:
If you are not sure which screens are used by Epics:
Following that topic, I've added new issue type above Epic name "Feature", When I create issue in Epic I see feature type available for creation under the epic. is it possible to remove it when click on "Create issue in epic" button?
A workaround I've used to counter this is to use an Automation rule - for example:
^ It keeps the data integrity high, and helps users learn what the hierarchy should be :)
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events