When using JIRA v6 OnDemand, how do I set up parent-child relationships across epics, features and issues?

Using JIRA 6.0 OnDemand, I would like to define an epic, define multiple features under an epic and then define multiple user stories under a feature. Then I should be able to link multiple test cases to a user story. How can I set up such relationships? Secondly, using JIRA 6.0 OnDemand version, how can I produce a "Requirements Traceability" report that lists all the epics, related features, user stories and test cases?

2 answers

0 votes
Jeff Curry Atlassian Team Jul 08, 2013

Sounds like you're asking for sub sub tasks which isn't currently available:


However you can use issue linking to setup hierachies as you describe ( which I admit are not as feature-full as subtasks ):


I believe JIRA's release notes feature should work as a requirements report:


We also have similar need with our client on stand alone JIRA

Client wants to map Epics - Features - Stories .

we need mapping Epics to Features to Stories, like how we map Epics and stories, not just links.

so that traceablity is better.

is there any other method to achive this, Atlassian is going to take longer time to develop this.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,923 views 19 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you