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

[Suhas Joshi]

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?

[Raju Adluru]

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.

Thanks.

[Jeff Curry]

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

https://jira.atlassian.com/browse/JRA-4446

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

https://confluence.atlassian.com/display/AOD/Linking+Issues

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

https://confluence.atlassian.com/display/AOD/Creating+Release+Notes