How to set Hierarchy for Initiative/ Epic

[Nate Dickinson]

I'd like to set the following hierarchy: 

1. theme
2. initiative
3. epic
4. requirement
5. task
6. sub task

How do I associate an epic to an initiative? I've done the below in issue type hierarchy, but when I go to an initiative and try to insert an epic in the epic link field I get the error. Do I need to use child link? 

[Philippe Puy]

At first set up the hierarchy in Advanced roadmaps.

Then in your issues use the field Parent link

[Trudy Claspill]

Adding to this...

You should be able to use the Parent Link or Parent field in the Epic to specify its parent Initiative. You won't be able to add an Epic to an Initiative from the Initiative issue view.

I note that you said you want the hierarchy to include

Epic > Requirement > Task

Do note that the Issue Hierarchy in Jira does not support adding a level between the built in Epic and the standard issue level directly below it. In order to make that structure you would have to rename you Epic issue type to Requirement, and then add another level above that (and below Initiative) for "Epic". However, "Epics" are a special issue type in Jira. Regardless of what you call it, only the original Epic issue type will get the special functionality associated with Epics. And if you do choose to rename it as "Requirement" that can potentially break third party apps that also have special functionality associated with the built in Epic issue type. For instance the ScriptRunner JQL functions for issuesInEpics() doesn't work if the built in Epic issue type is renamed.