Have you missed our video overview?
TEM main features quick tour

Test Environment Manager lets you update and share very easily the status and the deployed version of your various environments in JIRA.

Apwide TEM Overview Issue Details Environments Tab

Use as many Environment Custom Fields as you need to inform on which environments you have detected, tested, reproduced,.. an issue. Apwide TEM Overview Issue Page Environment Custom Fields Example

Apwide TEM Overview Environment Status Page Explained Light

What is an Environment ?

An environment in Environment Manager is basically defined by :

  1. An Application (ex : eCommerce, ERP, Mobile app,…)
  2. An Environment Category (ex : Staging, Production, Test, Development)
  3. An Environment Status (ex : “Available”, “In maintenance”, “Slow”,…)
  4. A deployed version (ex : ECOM 1.0.2)

Some these concepts depend on each other (ex : you cannot deploy an IOS version in a eCommerce environment). An environment can also have own properties (ex : URL to access the environment if applicable).

These concepts and their relations are modeled in the diagram below :

Apwide TEM Overview Environment Manager Concepts

Versions and Applications

Test Environment Manager re-use the concepts of Version that exists in JIRA (learn more about JIRA versions).

Optionally, an application defined in Environment Manager can be associated to a subset of Versions. For example, an “eCommerce” application could be associated to all versions of all projects starting with prefix “ECOM” (ex : “ECOM 1.2.3”, “ECOM 2.0”, “ECOM 3.beta”,…). It could also be associated to all versions of a specific JIRA project. These “Version Mapping” strategies is useful if you have a lot of different applications and if you use conventions to manage a clean versions repository in JIRA.

Note that if you have a lot of different applications, you can quickly get tons of version numbers to manage in the same JIRA project. Do not forget to archive old releases in order to limit the number of versions displayed on the various JIRA screens.

Application Schemes

Application Schemes is a set of applications that is associated to a JIRA project. It is mandatory to associate an Application Scheme to your project in order to see environment informations on your project’s issue pages.


Environment Manager is available on the Atlassian Market Place for both automatic or manual installation. Once installed, you have to complete this quick setup procedure to see Environment Manager in action on your JIRA instance.