Environment Custom Fields are used to link issues and Service Management tickets with Golive Environments.
Why Environment Custom Fields?
Linking your Jira issues to Golive Environments will enable your teams to build accurate statistics about the number of issues/tickets created, reproduced, tested,... in your various environments.
For example, you may add the following Environment Custom Fields to your "Bug" issues:
1.Detected in: Environment in which a new issue has been detected
2.Tested in: Environment in which a fixed issue has been tested
You can add up to 50 Custom Fields, so possibilities are just limited by your imagination
Environments to book
Environment Custom Fields can then be used to setup custom workflows that we deal with your environments, for example:
The concept of Environment Custom Fields is similar to the Version concept in Jira: you have only one inventory of Versions but you can have different Version fields on the same issue (ex: Fix Version/s and Affects Version/s).
Create an Environment Custom Field
You must be an Apwide administrator in order to create a new Environment Custom Field. On the Golive Page, click on “Global Settings” from the Settings menu.
Then open the Custom Fields tab:
Jira Server users could be confused, but Jira Cloud has changed the way third party Custom Fields are managed. From the Jira Cloud Custom Field configuration screen, you can only manage the fields provided by Jira Cloud platform. Apps have to manage Custom Fields on their side.
From here, you can create and delete Environment Custom Fields:
All attributes are mandatory and the key only supports "A-Z", "a-z" and "-" characters.
You will then need to add the newly created Custom Field to your issue types' screens accessible from Configure screens link. Refers to https://confluence.atlassian.com/adminjiracloud/add-a-custom-field-to-a-screen-991923749.html if you need clarifications about issue screen management.
Jira Cloud Custom Fields are not editable, so, be aware that you can only create and delete fields. However, if you delete a custom field, at the time you create a new one using the same Key, all of your data (eg: Jira issue reference) will be kept.
Select Environments on the Issue screen
If you configured an Environment Custom Field and added it to a Screen, you should be able to add Environments from the Issue screen:
The list of Environments that can be selected depends of the Project/Applications Setup. Only the Environments of the Applications linked to the current Jira Project will be displayed in the list.
Force Synchronization of Environment Custom Field options
Environment custom field is a multi-option field. Each Environment is represented by a specific Option having different properties (eg: category name, application name, etc.). Environment is an asset part of your Golive Environment Inventory, and Options are their copy in your Jira instance. On your issues, when you select a value for an Environment Custom Field, you select an option which refers to an Environment in your inventory. This means options must be maintained, synchronized, to represent the status of your Environment inventory. For example, each time an environment is created/deleted, its corresponding option is created/deleted as well.
Usually, this synchronization happens automatically under the hood. But it happens that options and Environment inventory differs, due to an action in Jira that Golive was not aware of (eg: restoration of a Jira backup, creation of a new project, etc.). You can consult the status of the synchronization from the Custom Fields page:
If Options and Environments differ, the number of differences is displayed in a yellow badge. If no badge, it means your Options are aligned with your Environments for this Custom Field.
By clicking on the Synchronize button, you have the detail of the differences:
One of the most common misalignment reason is an Environment that has been deleted but still referenced by issue:
If you want to solve this issue, you have to unset references to this Environments from the issues and trigger a new synchronization.