Xray Traceability report structure

[Paul Robert Cayanes]

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?

[Manuel]

Hi @Paul Robert Cayanes 

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.