This page list all the options available in the Miscellaneous configuration section.
Options related to the execution of test issues.
When this option is enabled, the overall Test Run status can be set directly, without depending on the status of manual Test steps or, in the case of Cucumber Scenario Outlines, Test examples.
When this option is enabled, Test Runs can be executed inline, directly from the Test Execution issue view page. This option is only available if the final Test Run Status (above) can be manually set.
When this option is enabled, the execution of tests is restricted to the Test Run's assignee.
When this option is enabled, whenever the status of a Test Run is changed to FAIL, all the Test Steps/Examples in TODO Status will also have their Statuses updated to FAIL.
When this option is enabled, the status of automated Test Runs can't be set manually. It can only be modified through the import of automated test results action.
When this option is enabled, the user can edit the Started On date in the Test Execution Details page.
When this option is enabled, the "Updated Date" of a Test Execution is updated when a Test Run is executed, and a History entry is created on the Test Execution.
Options related to the creation of Defect issue in the context of test execution.
When this option is enabled, the defects created in the context of a test run are automatically linked to the Test being executed.
When this option is enabled, the defects created in the context of a test run are automatically linked to the Test Execution issue.
When this option is enabled, the defects created in the context of a test run are automatically linked to the Requirement being tested.
Disallow Tests within certain workflow statuses from being executed or even added to Test Executions. Sometimes, a Test is still being written and should not be added to a Test Execution. In those cases, just indicate which Test workflow statuses are considered "not ready to be executed".
Choose the workflow statuses in which the Test Execution issues will not allow execution of Tests. For example, if you configure this list with the "Closed" status, then users are no longer able to execute Test Runs in this Test Execution issue when a Test Execution issue transitions to "Closed".
Choose what workflow status the test execution will transition to when a test run is executed.
Choose what workflow status the test execution will transition to when all the test runs are in a final status.
Choose what resolution will be applied to the test execution. This option is only available if the Resolved Test Execution workflow status is not none. The resolution is only changed for status of type done.
When this option is enable the cloned Test is linked with the Test Sets linked to the original Test.
When this option is enable the cloned Test is linked with the Test Plans linked to the original Test.
User Groups which are allowed to add/remove Xray notifications to the Notification Scheme in the project settings page, since it can affect other projects using the sameNotification Scheme.
Final Test Run statuses that may trigger the 'Test Run Status set to Final' or 'Precedent Test Run Status set to Final' events.
When this option is enabled, the Test Repository and the Test Plan Board will be enabled and accessible from the top menu and the project sidebar.
The project roles that are allowed to edit the Test Repository. If no role is specified, then every user is able to modify the Test Repository.
When this option is enabled, the Automated Steps Library will be enabled and accessible from the top menu and the project sidebar.
When this option is enabled, the Cucumber Scenarios will be validated before creating or updating a test.
The defects created in the context of a test run are populated with the "Environment" value from the Issue Type selected in this field
When this option is enabled, the description field of the defects created in the context of a manual test step result, will default to a table containing the steps of the test and the actual results until the step where the defect is being created.
When this option is enabled, the Affect Version field of the defects created in the context of a test run will be populated by the FixVersion value of the Test Execution.
The defects created in the context of a test run are populated with the Label value from the Issue Type selected in this field
When this option is enabled, the Pre-Condition web panel on the Test issue view screen will be displayed above the Test Details panel.
When this option is enabled, the cells of the Manual Test Steps table will be displayed in short-view mode. If this mode is enabled, the rows will have a limited height to allow for better page navigation. There is an expand option within each cell to view the complete content.
When this option is enabled, the test definition will be deleted when changing Test Type. If this option is disabled, the test definition won't be deleted and it'll be possible to undo the Test Type change operation and keep the information.
When this option is enabled Project admins have permission to configure Test Step Custom Fields.
When this option is enabled Project admins have permission to configure Test Run Custom Fields.
User Groups that are allowed to add Xray Issue Types to a project in the project settings. If no user group is specified, then no one is able to add Xray issue types from the project settings page.
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 issues:
Choose the language in which the automated Cucumber tests will be exported in. The default language is English.
When this option is enabled, the dashes in the issue keys included in the exported Cucumber feature files will be replaced by underscores. Enable this option if your testing framework does not support dashes in tags.
When this option is enabled, one feature file will be generated for each requirement issue within the export context. Disabling this option will generate all tests in the same feature file, given that all tests also have the same background (pre-condition) or they have no background.
When this option is enabled, Jira users will be able to generate documents based on the templates installed. Disabling this option will remove Doc. Generator action from all the screens where it's available.
Maximum number of issues that can be Exported using the Document Generator (default is 1000, but the value can be adjusted between 1 and 10000). Exporting high number of issues at the same time may affect the performance of your Jira instance. If exceeded, then you need to adjust the filter being used or adjust this setting instead.
Options related to the execution of test issues.
Maximum number of Test Runs a user can select for bulk operations in the Test Execution view page (default is 100).
Maximum number of requirements that can be shown in the Overall and Historical Requirement Coverage reports/gadgets (default is 10000). If exceeded, then you need to adjust the filter being used or adjust this setting instead.
Sets the upper limit of Tests used by the Test Evolution Gadget. This might be useful for handling performance issues.
Some endpoints results are paginated. This configuration defines the number of objects returned in each set of paginated results. Any try to make a REST API call that returns more than this number of results will result in a error.
The maximum number of characters a parameter value can have. The default value is 100, the minimum is 64 and the maximum is 255 characters.
Sets the thread pool size used for calculation of TestRunStatus and Requirement Status fields, which are related to the calculation of the status of Tests and the coverage of requirements.
It's used to avoid resource starvation (CPU and BD) in more intensive CI/CD scenarios due to the triggered coverage calculation.
A high number allows Xray to produce results faster but will eventually use more CPU resources.
It should be between 1 and max number of CPU threads.
When this option is enabled, we will collect some anonymous data concerning general usage of Xray. This data will be sent to Xblend for internal usage only and will allow us to improve the overall user experience and existing features. Please read the privacy policy for more details.