The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Generating a requirements traceability report
sclemons
I'm New Here 
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 10, 2021 edited
Hi, We have an instance that we are using for requirements tracking. We have created outward links from the customer to system to subsystem to test projects. When we try to run a report using several plugins we are not seeing the results as expected. If there is a single trace down the chain we are good, but is a system issue outwardly traces to 2 subsystem issues the hierarchy doesn't look right. It pushes one of the system requirements until the subsystem requirement. Any ideas? Have tried with impact for jira and links heirarchy.
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
TAGS
Community showcase
Atlassian Community Events
Copyright © 2026 Atlassian