Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What's the difference between the usage of Capability and Initiative?

I am trying to create a hierarchy for some of the teams who are using the User stories and Epics format. What is the right method of using Capability and Initiative in Jira?

Does the following structure make sense for reporting and end to end project mapping?

  1. Initiative -> Capability (multiple) -> Epics (several for each Capability) -> Stories.

Happy to hear thoughts about using Features too but the teams are not using it so might not be encouraged. 

1 answer

1 accepted

1 vote
Answer accepted

Hi Shripad,

Any levels of hierarchy above the epic level is considered an initiative per the terminology definitions on the structure of the hierarchy.  So your Capability hierarchy level is the first Initiative layer and Initiative hierarchy is the second initiative level as the top level grouping.  

Initiatives work on a parent to child mapping, A single 'initiative' hierarchy is a very large body of work, which is the parent of the epics linked as the child issues at the next level below the Initiative, and the Next Initiative hierarchy above the first is a similar grouping but instead of grouping the epics it is a grouping of the child Initiatives at the next layer down.

The best way to think of Initiatives is as a method to create categories that encompass a specific body of work that needs to be tracked as a single entity due to the relationship of those items.  But overall a categorization effort for like items becoming more and more broad of a term the higher up the hierarchy you go.

A really good break down on the layering can be seen in this blog post: "Epics, Stories, Themes, and Initiatives"


Hi Earl,


Thank you for the detailed explanation. It gives me a fair idea about the structure and hierarchy, which I wanted to understand.


I had read the article before posting it :)

The challenge is, not many fields are enabled/encouraged to be utilised at this stage - including Features and Themes.


Having said that, your answer helps and suffices my question. Thankyou.




Like # people like this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: https / Keeping on top of your dependencies is a key part of ensuring project success....

1,438 views 11 18
Read article

Community Events

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

Events near you