Page History
...
The "Requirement Status" custom field is a calculated field, usable in the context of requirement issues, that calculates the requirement coverage for a specific version. The version that it calculates the coverage for depends on the behavior for that field defined in a global configuration (see configuration details details here).
As an example, you may prefer to always calculate this based on the latest test run(s), independently in which version it/they was/were executed... or you may prefer to calculate it for the earliest version yet to be released (i.e. the next version). In the later case, it takes into account the order of the versions within the project settings page.
...
| Info | ||
|---|---|---|
| ||
| For more information on Requirement Status calculation please see Requirement Requirements Coverage Analysis. |
Revision
The system revision (or code revision) being tested in the context of a given Test Execution. It is an open field that can contain the Git commit hash or the SVN revision, for example. Some users use it to put the build number/identifier.
...
The "TestRunStatus" custom field is a calculated field, usable in the context of Test issues, that calculates the "status" (not the workflow status) of the Test for a specific version, having in mind executions (i.e. test runs) for that version. The version that it calculates the status for depends on the behavior behaviour for that field defined in a global configuration (see configuration details details here).
The calculated value for the field also depends on Test Environments, if they're being used, as mentioned here. As an example, you may prefer to always show the latest test run result independently in which version it was executed... or you may prefer to show the status of the latest run executed on the earliest version yet to be released (i.e. the next version). In the later case, it takes into account the order of the versions within the project settings page.
...
The Test Environment(s) associated to a given Test Execution. This is an open field, similar to a label; you should try to reuse existing Test Environments. It may be empty (default).
Test Execution Defects
Shows the number of defect issues associated with a Test Execution issue. These can be directly linked with the issue using JIRA issue links or defects that were created during testing within Test Runs.
Test Execution Status
This custom field provides information about the progress (i.e. the "Overall Execution Status") of the Test Execution issue.
It can be used, for example, in gadgets, included in the cards of Agile boards, used as a column in JIRA issues listing.
This field is non-searchable.
Test Set Status
The "Test Set Status" custom field is a calculated field, usable in the context of Test Set issues, that calculates the "status" (not the workflow status) of all the Tests within the Test Set, for a specific version, having in mind executions (i.e. test runs) for that version. The version that it calculates the status for depends on the behavior behaviour for that field defined in a global configuration (see configuration details details here).
Although a Test Set in Xray is basically a list of Tests,thus not related with any execution whatsoever, you can add this field to the Test Ser view screen as a way to have a glance of the current status of the Tests that are part of it, for some version right from the screen of the Test Set. This can be quite useful if you have some highly relevant Test Sets and you wish to quickly have an high-level idea of the status of the Tests that belong to it.
This field is non-searchable.
Test Execution Defects
Shows the number of defect issues associated with a Test Execution issue. These can be directly linked with the issue using JIRA issue links or defects that were created during testing within Test Runs.
Test Execution Status
This custom field provides information about the progress (i.e. the "Overall Execution Status") of the Test Execution issue.
It can be used, for example, in gadgets, included in the cards of Agile boards, used as a column in JIRA issues listing.
This field is non-searchable.
Test Plan Status
...