Can I roll a Story test coverage status up to its parent Epic?

[Avimanyu Chakraborty]

Hi,

Considering an example where I create two Stories under an Epic. Now, I create some Xray tests under each Story so that the Story requirements are covered.

When I go back to the Story's parent Epic, is there a way to determine the requirement coverage at the Epic level (I have not created any Xray tests directly under Epic though)?

Thanks,

Avi.

[José Domingues _Xray_]

Hi Avimanyu,

Yes, Xray supports the notion of parent and sub-requirements as long as they are both configured to be handled as requirements.

Please have a look at this blog post which details this in full detail: https://www.xpand-addons.com/xray-sub-requirements/

Best regards,

Xray Team

[Avimanyu Chakraborty]

Hi Xray Team,

Thank you for your response. The documentation you have shared does clarify my query for Epic-Story relation.

I have an additional related query.

I have created a new custom issue type (or a third-party add-on issue type) which sits above Epic issue so that multiple Epics can be grouped together.

In this case, how would I map my custom issue type to Epics as Xray requirement sub-requirement coverage?

[José Domingues _Xray_]

Hi Avimanyu,

Officially, Xray currently provides two levels of hierarchy for "requirements"; that hierarchy may be configured in multiple ways as detailed in the blog post or in our documentation page: https://confluence.xpand-addons.com/display/XRAY/Requirements+and+Defects#RequirementsandDefects-Sub-Requirements .

There is a small caveat though; you may enable the Epic/Story relation and an additional parent/sub-requirement relation, based on a specific issue link that you define.

This will allow you to evaluate the coverage on the upper entity (taking into account all the coverage for all the descendant requirement), although the reports won't show the complete hierarchical relation. Again, this is something possible but it's not really an official feature since it's not fully implemented in a consistent manner.

Best regards,

Xray Team

[Tim Schächterle]

Hi, in our case we also may use more than 2 levels.

What are the current restrictions?

Will it be an official feature in future?

Regards, Tim

[Inês Silva]

Hi Tim

As of v3.3, Xray officially supports two levels of requirements using one of the relations mentioned here: https://confluence.xpand-it.com/display/XRAY/Requirements+and+Defects#RequirementsandDefects-Sub-Requirements 

We do have multi-level support for coverage analysis, including for our Traceability Report, in our backlog: https://jira.xpand-it.com/browse/XRAY-2651 

Please review and vote on it, so that we are able to track your interest on it.

Best regards,

Xray Team