I would like to manage functional requirements by functional area and have traceability from high level functional requirements through to associated stories, development and then implementation. At the the moment it is all at an EPIC and issue level. There is much detail (technical, testing etc) I can't see what we are supposed to be delivering (I.e.what the client is paying for.) Can an EPIC belong to a Project Area that would belong to a Project that would belong to a Programme?
JIRA doesn't have relationships above the project level. You can imitate that with naming conventions, but I don't think that is what you're looking for. It sounds like you want a parent to child to grandchild type relationship, correct?
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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