Introduction

Xray provides project administrators with various configuration options to fine-tune Test management behavior at the project level. The Miscellaneous Settings section allows admins to customize test execution, defect management, workflow restrictions, cloning behaviors, and other key aspects of Xray's functionality.

By default, projects inherit globally defined Miscellaneous Settings, ensuring consistency across all projects. However, project administrators can override some of these settings to better align Xray's behavior with their team's specific needs.

This page explains how project admins can:

Override global Miscellaneous Settings at the project level.
Configure test execution options, including workflow restrictions and status tracking.
Define defect management rules to control how defects are linked within Xray.
Customize cloning behavior for Tests, Test Sets, and Test Plans.
Set default values for defects and Test-related fields.

Customizing these settings allows teams to optimize their testing workflows, enforce project-specific rules, and improve overall Test management efficiency.

Not all settings can be overridden at the project level. Some configurations remain globally controlled and can only be modified by Jira administrators.

All the Miscellaneous project settings will be transferred during a migration from Server/Data Center to Cloud.

Access

In your Jira Server/DC instance, click the settings/gear icon (Figure 1 - 1) and select Projects (Figure 1 - 2).

A list of projects appears (Figure 1 - 3). Click the project you wish to work on.

Figure 1 - Settings

An Xray Settings menu will appear on the left side of the screen. There, click Miscellaneous (Figure 2 - 1).

The Miscellaneous page will open (Figure 2).

Figure 2 - Miscellaneous

In the Miscellaneous (Figure 2), you can edit the different fields to customize your experience (Figure 1 - 3).

Once you've finished editing, click Save (Figure 3 - 1).

Figure 3 - Save

Operations

Overriding Global Miscellaneous Settings

By default, each project inherits the globally-defined Miscellaneous Settings. However, project admins can override the global settings at the project level directly.

Not all settings can be customized at the project level. Some configurations are managed globally and can only be modified by Jira administrators. This means the settings available in the project configuration may not include all the options found in the global settings.

For project admins to override the global miscellaneous settings they must enable the Override global settings toggle (Figure 4 - 2).

Once the toggle is enabled for the first time in the project, the current global settings will be copied to the project so that project admins can start from the global (default) configuration.

You can disable project-level settings at any time by toggling off the Override global settings option (Figure 4 - 2). If you re-enable the project settings, they will be restored to their last set values: you can't restore "default" settings at the project level. If you wish to revert to global settings, simply turn off the project-level settings for the project using the Override global settings toggle (Figure 4 - 2).

Configuring Miscellaneous Settings

Test

Figure 4 - Test

Display the Precondition Section Before the Test Details

When this option is enabled (Figure 4 - 1), the Precondition web panel on the Test Issue view screen will be displayed above the Test Details panel.

Display Manual Test Steps Table in Short View

When this option is enabled (Figure 4 - 1), 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.

Test Run Options

Options related to the execution of Test Issues (Figure 5 - 1).

Figure 5 - Options

Set Final Test Run Status

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.

Inline Execute Tests

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.

Restrict Tests Execution to Assignee

When this option is enabled, the execution of Tests is restricted to the Test Run's assignee.

Fail All Steps/Examples

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.

Restrict Automated Test Status

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.

Can Edit TestRun Dates

When this option is enabled, the user can edit the Started On date on the Test Execution Details page.

Track Time

When this option is enabled, the Time Tracker module is displayed.

Set the Value of the Time Tracker

When this option is enabled, the user can set the timer value of the Time Tracker.

Enable Test Run Status History Log in Test Executions

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.

Defect Issue Links

Options related to the creation of Defect Issues in the context of Test Execution (Figure 5 - 2).

Link Defects with Test

When this option is enabled, the defects created in the context of a test run are automatically linked to the Test being executed.

Link Defects with Test Execution

When this option is enabled, the defects created in the context of a test run are automatically linked to the Test Execution issue.

Link Defects with Requirement

When this option is enabled, the defects created in the context of a test run are automatically linked to the Requirement being tested.

Workflow Statuses (Figure 6 - 1)

Figure 6 - Options

Disallow Executions of Tests with Workflow Statuses

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".

Disallow Executions with Workflow Statuses

Choose the workflow statuses in which the Test Execution Issues will not allow the 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".

In Progress Test Execution Workflow Status

Choose what workflow status the Test Execution will transition to when a Test Run is executed.

Resolved Test Execution Workflow Status

Choose what workflow status the Test Execution will transition to when all the Test Runs are in a final status.

Resolution for Resolved Test Execution

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 the type Done.

Clone Issues (Figure 6 - 2)

Associate a Cloned Test with all Original Test Sets/Test Plans

When this option is enabled, the cloned Test is linked with the Test Sets/Test Plans linked to the original Test.

Defect Default Values (Figure 6 - 3)

Environment

The Defects created in the context of a Test Run are populated with the Environment value from the Issue Type selected in this field.

Include Steps Table in Description

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.

Include Version

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.

Label

The Defects created in the context of a Test Run are populated with the Label value from the Issue Type selected in this field.

Components

The Defects created in the context of a Test Run are populated with the Component value from the Issue Type selected in this field.

If you have questions or technical issues, please contact the Support team via the Customer Portal (Jira service management) or send us a message using the in-app chat.