How can XRay deal with requirements that became invalid for a new version?

[Daniel Hertrich]

In many software projects, requirements don't live forever.

Requirement R1 may be valid for versions 1.0 to 3.0, but in version 4.0 it may not be a requirement anymore. But it's still in JIRA and linked to an XRay test (case).

We considered to mark such requirements with a custom field "invalid from version", where we would put "4.0" into, but I assume that makes automated recognition of XRay, that this requirement isn't to be used anymore (hence the linked test isn't to be tested anymore) in v4.0, rather difficult. 

Another solution could be a status field, e.g. with values "valid" and "invalid".

What is the recommended way to set up JIRA with XRay, so that only the requirements need to be altered, but not the links to the tests or the tests themselves? 

Thank you!

[José Domingues _Xray_]

Hi Daniel Hertrich,

You can ignore requirements with a specific status or label and they won't be included in the Requirement Coverage calculations.
For instance, you can tell Xray that all requirement issues with the workflows status "Closed" should be excluded from requirement coverage calculations. The same happens with labels: if a requirement has a label which is marked as a "not to be tested" label, it'll be excluded from requirement coverage calculations as well.

You can find more information about it in our documentation: Ignoring Requirements.

Best regards,

Xpand Add-ons Team