Configure Test Run Properties to record where and when testing takes place. In each Jira space, you can enable Environment, Sprint, and Version, and decide which values testers must provide.

Before you begin

Sign in with Jira administrator or Jira space administrator permission.
Choose the Jira space whose execution settings you want to change.
Make sure the environments, Jira sprints, and versions your testers need are available before making them mandatory.

1. Open Test Run Properties

Open your Jira space and select Vansah.
Select the Settings gear, then Settings and Compliance.
Select Space Settings in the left menu.
Select Test Run Properties in the settings menu.

The screenshot shows an earlier settings layout. The Environment, Sprint, and Version controls remain in Test Run Properties.

2. Choose optional or mandatory properties

Property	Enable control	What testers record
Environment	Enable Environments	The test environment, such as UAT or Staging.
Sprint	Enable Sprint for Vansah Test Case Execution	The Jira sprint associated with the execution.
Version	Enable Versions	The Jira version associated with the execution.

Select the property’s Enable checkbox to make it available.
Leave Mandatory for Test Run cleared if the value is optional.
Select Mandatory for Test Run if testers must supply a valid value before the required execution action can continue.

The Mandatory checkbox appears after the property is enabled. A mandatory setting is enforced only while the property is enabled. Clearing Enable hides its related controls; it does not delete existing Test Runs.

For example, enable Environment and make it mandatory when every execution must identify the system being tested. Keep Sprint optional if your team also tests outside sprints.

3. Set linked Sprint and Version choices

When testing from a Jira work item, you can narrow the choices offered from that work item:

Setting	When selected
Only show sprints linked to Jira Work Item	Uses the sprint associated with the Jira work item when preparing its execution choices.
Only show Versions linked to Jira Work Item	Uses the work item’s Fix versions when preparing its execution choices.

Clear the relevant checkbox if testers need the available Jira space versions or sprints from its boards instead. A work item without a sprint or Fix version can have no linked value to offer.

These options control work item-based selection lists. Folder execution and an opened Test Run can use broader Jira space lists, so check the actual execution view your team uses.

4. Confirm the saved settings

Wait for the success message after each change. Changes save immediately; there is no separate Save button on this panel.
Reopen Test Run Properties to confirm that your choices were retained.
Return to the intended Test Case or Test Plan execution and review Run Setup. Confirm that the expected properties and choices are available.
Tell testers which values they should use. If required properties are highlighted, select valid values before continuing.

If you make a property mandatory while an older Test Run has no value, testers may need to complete its Run Setup before recording further results. See Executing Test Cases: Overview for the execution workflow.

Troubleshoot property setup

Issue	What to check
You cannot change the settings	Confirm Jira or Jira space administrator permission.
A property is not visible during execution	Check its Enable setting in the execution’s Jira space and reopen or refresh the execution view.
No Sprint or Version choices appear	Check the work item’s sprint or Fix versions when linked-only selection is enabled. Check the Jira space’s versions and accessible boards when broader selection is used.
Execution asks for a required value	Select a valid Environment, Sprint, or Version in Run Setup. Making a field mandatory does not create a value for it.
A setting changes back after reopening	Check for an error message and wait for each save to complete before changing another option. Ask your administrator to investigate if it continues.