Tracking a requirement is not exactly scrum, so JIRA doesn't have an easy way to deal with that natively.
If it's just a one-time need, maybe you could use an Epic as the requirement, and link it to the related stories.
If that's a recurrent need, then you need some sort of new methodology.
This is something interesting that you could look at. SAFe is vast and somewhat complex, but here are some basic tips:
Now, point 3 is the tricky part. The Structure plugin would let you make a complex hierachy of issues, so you'd have requirement>epic>story>subtask. It's really neat and lets you see sums of estimated and spent times, so you have a very quick view of everything related to the requirement.
That plugin is a bit expensive though. And not exactly easy to configure in such a way that the hierarchy would be automatic, and not just you manually drag and dropping issues around.
There might be other plugins out there that do something that would help you. But I think Issue Links are the key here.
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