On this page

Global Environments

Appsvio Test Management (ATM) keeps one global list of test environments, for example Test, Staging, or Production. You choose the environment of a Test Execution in its ATM Environments field.

With environments, you can run one Test Plan several times, once for each environment. Each run is a separate Test Execution. You can also run a Test Plan many times on the same environment.

Open the Environments page

In the Jira sidebar, go to Apps › Test Management › Testing Projects.
Click Configuration in the top right corner of the page. Only Jira administrators see this button. See Permissions.
The Configuration page has two sections: Environments and Test steps. Select Environments.

The table lists all environments with their Name, Description, Url, and status: Active or Disabled. Each row has a … menu.

The Environments section of the Configuration page. The table lists environments with their Name, Description, Url, and status, and each row has a … menu. The Create Environment button is above the table.

Create an environment

Click Create Environment.
Enter a Name, for example Staging. The name is required.
Optionally, enter a Description and a Url.
Click Create. To close the window without saving, click Cancel.

The Create Environment window with the required Name field, the Description and Url fields, and the Cancel and Create buttons.

Disable or enable an environment

To disable an active environment, open the … menu in its row and select Disable.
To turn a disabled environment back on, open the … menu and select Enable.

The … menu of a disabled environment in the Environments table, with the Enable option that turns the environment back on.

Where environments are used

On a Test Execution, you set the environment in ATM Environments. When you create a Test Execution from a Test Plan, you can pick it right away. See Create Test Execution.
During a test run, the execution window of a Test Case Execution shows ATM Environments as a read-only field. See Test Steps Execution.
On defects, you can add the ATM Environments field to the screen. Then you can search defects by environment. See Defects.
With JQL, you can search Test Executions by environment and version. See Using Jira Fields.
The Coverage Report has an ATM Environments filter. See Coverage Report.
The Testing Project Dashboard shows a chart of Test Executions by environment. Test Executions without an environment are in the No environment group. See Testing Project Dashboard.

ATM Environments is the usual place for the environment of a Test Execution. If your process needs it, you can keep the environment in another field instead. For all fields that ATM adds to Jira, see ATM in Jira.