Page History

...

Have in mind that a requirement  is assigned to and implemented in some version. However the requirement will still live after that version, at least for some time. Therefore, when someone mentions a "status of  a requirement", you have to ask "In which version?". The status of the requirement is thus dependant on the executions you make for the associated Tests in some version of the system, which may by different from the version in which the requirement was initialy implemented in.

In the following example, the first image shows the calculated value for the status of requirement for the next to be released version (i.e. v3.0), while the second image shows the calculated values for all the unreleased versions. This behaviour was changed in Custom Fields Preferences, in Xray settings.

Image Added Image Added

This field is searchable, so you can make statistics with it or use in gadgets. However, if you wish to search for requirements in some status we recommend using the the requirements() JQL function instead (more info info here). Image Removed Image RemovedYou can also add it to your cards of your Agile boards, to have real-time feedback of its status shared across your team members.

TestRunStatus

Whenever we're speaking about status associated with a Test, we may in fact be talking about different things:

...