I have been through several JIRA and Confluence add-ons for managing requirements being:
However, from my understanding none of the above add-ons is able to achieve all the followings:
I have the same question. In the meantime, to get around this traceability issue on my end and many other obstacles, I have built a prototyping software that allows an end user to mock-up what the end product might look like, while capturing the business requirement IDs of other repositories like JIRA, Confluence, HP's QC/ALM, etc. for each field component and each form. This software exports everything into PDF and Word. It might not work exactly like you might want it to, but it's good start in my opinion. Here's a little bit about it: https://www.youtube.com/watch?v=t9SJmoM30aE. If you're interested in checking it out, I'll send you a free copy if you e-mail me at: firstname.lastname@example.org.
Hopefully Atlassian can tell us how to do what you're asking within their suite of products, or add it as a new feature.
We have a standalone Clouds application: Matrix Requirements Medical that does exactly what you ask.
It is linked to JIRA through an add-on that allows you to link a missing requirement to a JIRA ticket asking someone to add the functionality, or to JIRA ticket for a failed test etc.
It is called Medical because on top of the features you require we also have the ability to deal with Risk management per ISO14971. This is an optional module.
co-founder, Matrix Requirements GmbH
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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