You can access all the screens of the add-on from the “Environments” top menu:

N.B. In order to do certain setups of Environment Manager, you must log as a Jira Administrator (your account must be a member of “jira-administrators” group).



Step 1: Setup your applications

You must define every application you want to manage in Environment Manager.

  1. Click on “Manage Applications” menu item
  2. Edit or create an application choosing the right application scheme
  3. (Optional) Set the “Mapped Versions” options : they allow you to define which versions are mapped to you application. If you have any doubt : do not set any mapping options, you will be able to refine the version mapping later.

Apwide TEM BasicSetup Manage Applications Edit
More About “Mapped Versions” options :
Imagine that you create an application called “eCommerce”. You can decide that only version names starting with “ECOM” Version Prefix (ex : ECOM 1.2.3, ECOM v5.6beta,…) are valid to be used as deployed versions for “eCommerce” environments (like in the example shown above). You can also define that all versions from a specific JIRA project are valid versions for “eCommerce” environments. Note that both version prefix and projects can be combined.


Step 2: Setup your environment categories

  1. Click on “Manage Categories” menu item
  2. Edit or create a category (ex : “Staging”, “Pre-production”, “Test”, “Integration 1”, “Integration 2”, “Dev 1”, “Dev 2”,..).
  3. Change the default display order of the environment categories using the “up”/“down” button in the list

Note that you have to setup all possible environment categories even if they are not available for every applications.


Step 3: Setup your environments

  1. Click on “All Environments” menu item to get the list of all existing environments
  2. Create or edit an existing environment
  3. Choose the application and the category of the environment (ex : “eCommerce – Staging”)
  4. If applicable, you can also set the URL to access the environment
  5. Set other custom properties (by default : “description” and “details”) : content can be multiline. URL and e-mail addresses will be automatically detected, shorten for display and converted into html links. It is specially useful if you want to add convenient shortcuts to admin console, alternate links, e-mail address of administrators,… to make these environment information easily available for JIRA users.

Step 4: Configure your JIRA projects

Since version 4.4, all JIRA projects are associated by default to the single Application Scheme that is created during first installation.

Read Project Configuration documentation for more advanced settings.

N.B. For versions prior to 4.4, no Application Scheme is associated by default to JIRA projects. You have to manually associate each of your JIRA Projects to an Application Scheme using Project Administration pages as described here.