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?
if you configure Epic, Story and also Subtasks as coverable issues/requirements that you can cover with tests, then those will appear on the Traceability report that Xray provides.
Please have a look at this page as it details the different levels of requirements you can have.
There's also an app for Confluence named Xray Reports for Confluence that can serve this purpose as well, if you're using Xray for Test Management and want to see traceability within Confluence.
This app allows you to embed testing reports, based on data from Xray Test Management, directly into your pages in Confluence. It provides several macros tailored for this, that allow you, for example, to track traceability.
That macro provides preview on the results, before publishing the page, and allows interaction with the chart, for example to expand epics and see the related story issues.
To get it working, you'll need to follow these steps, which require installing not just this app on Confluence but also a "Connector" app in your Jira instance:
More info on the installation steps here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.