Issue Hierarchy Best Practices

[Ashley Zimmerman]

Hello!

We're being asked to review an additional hierarchy level for our instance and I've heard concerns around how additional "layers" of hierarchy can cause complication and even limitations with integrations.  Currently we have Initiative > Capability > Epic > Tasks.  I believe this structure fits well with add ons like Jira Align.  Is this true?  

If we were to add Feature between Initiative and Capability we would need additional customization to implement Align correct?  What other reasons / concerns are there when implementing additional layers of hierarchy?

Thank you!

[Nikola Perisic]

Welcome @Ashley Zimmerman 

I don't know where have you heard that this is best for Jira Align. Issue hierarchy needs to suit your needs and the way you want to structure your hierarchy. Agile is defined with Epic -> Story -> Task -> Sub-task hierarchy. You can modify this however you would like, as long it does the job for you.