Page History
...
Upon Xray installation, the following custom fields are created in your JIRA installation. These custom fields are required for the normal operation of Xray. If these custom fields are not correctly configured for Xray issue types, you'll probably experience errors. All Xray custom fields are included in the JIRA "Default Field Configuration". If you have specific field configurations for your projects please make sure to also include the Xray custom fields in these field configurations.
Info | ||
---|---|---|
| ||
For a more detailed explanation of each custom field provided by Xray, please give a look at Using custom fields. |
Name | Type | Available Context(s) | Screens |
---|---|---|---|
Begin Date The start date for the Test Execution or Test Plan | Date Time Picker | Issue type(s): |
|
Conditions The Pre-Condition conditions | Pre-Conditions Editor | Issue type(s): |
|
Cucumber Scenario The Cucumber Scenario clauses in Gherkin | Cucumber Test Steps Editor | Issue type(s): |
|
Cucumber Test Type The Cucumber Scenario Type | Automated Test Type Select List (single choice) | Issue type(s): |
|
End Date The finish date for the test execution | Date Time Picker | Issue type(s): |
|
Generic Test Definition The definition for automated generic Test | Generic Test Editor | Issue type(s): |
|
Manual Test Steps The manual steps fields, in JSON format | Manual Test Steps | Issue type(s): |
|
Manual Test Steps (Export) The manual steps fields for exporting manual tests | Manual Test Steps (Export View) | Issue type(s): | |
Pre-Condition Type Choose the Pre-Condition Type. It must match the Test Type to which this Pre-Condition is associated | Pre-Condition Type Select List (single choice) | Issue type(s): |
|
Pre-Condition association with a Test The Pre-Condition issue to associate with this Test | Pre-Condition Association with a Test | Issue type(s): | |
Requirement Status* Requirement status | Requirement Status Custom Field |
| |
Revision The system revision for the test execution | Text Field (single line) | Issue type(s): |
|
Steps Count Number of Steps in a Manual Test | Manual Test Steps Count | Issue type(s): | |
Test Execution Status The overall execution status for the tests in the test execution | Execution Status Custom Field | Issue type(s): | |
Test Set Status* The execution status for the tests in the test set | Execution Status Custom Field | Issue type(s): | |
Test Sets association with a Test Start typing to get a list of possible matches or press down to select from a list of existing Test Sets to associate with this Test | Test Sets Picker | Issue type(s): |
|
Test Type Choose the Test Type | Test Type Select List (single choice) | Issue type(s): |
|
TestRunStatus* Latest Test Run final status | Test Run Status Custom Field | Issue type(s): | |
Tests association with a Test Execution Associated Tests with this Test Execution | Test Execution association with Tests | Issue type(s): | |
Tests association with a Test Set Associated Tests with this Test Set | Tests Picker | Issue type(s): | |
Test Plan Status The aggregated execution status for the tests in the test plan | Test Plan Status Custom Field | Issue type(s): | |
Tests Count Number of Tests within a Test Set or a Test Plan issue | Issue Links Count | Issue type(s): | |
Test Environments Test Environment(s) associated with the Test Execution. | Test Environments Custom Field | Issue type(s): |
|
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 Defects | Issue type(s): |
Info | ||
---|---|---|
| ||
(*) For more information on Requirement Status please see Requirement Coverage Analysis.More info on These fields (i.e. TestRunStatus, Test Set Status and Requirement Status may be found ) behaviour depend on a configuration that is detailed in the page Custom Fields Preferences. |
...