Issue Hierarchy Best Practices

Ashley Zimmerman
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 31, 2024

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!

1 answer

2 votes
Nikola Perisic
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 31, 2024

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events