Page History
The options available in Custom Fields Preferences are:
| Table of Contents |
|---|
| Note |
|---|
A JIRA Jira re-index operation is recommended when recommended if there are changes to the following options. |
...
Choose which version is used for calculating to calculate the Test Run Status Custom Field. The available options are:
...
When this option is enabled, the status of the Test is calculated based in the latest TestRun independently on , regardless of the version it was executed.
Earliest Unreleased Version
...
When this option is enabled, the status of the Test is calculated based in the latest TestRun executed on the first Fix Version explicitly assigned to the Test.
| Note |
|---|
The "Test Run Status" custom field value will depend on the Test Environments, if they are being used. Please see Working with Test Environments. |
Test Set Status Custom Field Version
Choose which version is used for calculating to calculate the Test Set Status Custom Field. The available options are:
...
When this option is enabled, the status of each Test in the Test Set is calculated based in the latest TestRun independently on , regardless of the version it was executed.
Earliest Unreleased Version
...
When generating Cucumber .feature files, the issue keys are included as labels in the feature. This option allows you to prefix the generated label keys to identify the scenario with the following JIRA Jira issues.:
- Test;
- Test Set;
- Requirement;
Requirement Status Custom Field Versions
...
When this option is enabled, the status of each Test associated with the Requirement is calculated based in the latest TestRun independently on , regardless of the version it was executed.
Earliest Unreleased Version
...
When this option is enabled, all explicitly assigned Fix Versions are displayed in the Custom Field.