You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We're building up our JIRA issue type layer structures and we're looking at how the Requirement status value rolls up from a Test that's attached to the lowest Requirement issue type.
In doing so, I see that the Traceability report captures only Epic -> Story -> Subtask structure. When our Epic is a child of an Initiative/Capability (or any issuetype we set as parent of Epic), the parent ticket is displayed separately and not part of the traceability. Also it seems that the Requirement status is not reflected to the parent ticket.
Is this a limitation in Xray?