Populate Jira Approvers from Golive Environment Configuration

In this guide, you’ll learn how to use Jira Automation and Golive to automatically populate the Approvers field in Jira work items using approvers defined at the Environment level in Golive.

This setup retrieves approver names stored as a Golive Environment Attribute and maps them to Jira users, ensuring that bookings, changes, or blackouts always include the correct approvers without manual input.

Requirements

Golive Cloud installed on Jira Cloud.
Approvers attribute configured on Golive Environments:
- Markdown type.
- Jira usernames separated by commas.
Admin permissions to create or modify Jira Automation rules.
A Jira work item type for bookings / changes / blackouts with:
- Environments field.
- Approvers field available on the screen.

Configuration Overview

You'll configure one Jira Automation rule that performs the following actions when a work item is created:

Retrieves the selected Environment ID from the issue.
Fetches the list of Approvers from Golive.
Splits the Approver List into individual values.
Resolves each approver to a Jira User ID.
Adds each user to the Jira Approvers field
Logs values for traceability.
Adds a comment for verification.

Configuration Steps

Step 1: Define the Trigger

Trigger: Work item created

Configure the rule to trigger on creation of the relevant work item type.
You can add additional conditions if required.

Step 2: Send Web Request – Get Selected Environment ID

Web request URL:

CODE

https://golive.apwide.net/api/customfield/environment/selected?issueKey={{triggerissue.key}}&customfieldId=customfield_10487

HTTP method: GET

Headers:

api-key: Generate a Golive API Token and paste it as value.

Important

Replace customfield_10487 with the ID of your Environment custom field.
Enable Delay execution of subsequent rule actions until response is received.

Step 3: Create Variable – Environment ID

Variable name: EnvID

Smart value:

CODE

{{webresponse.body.items.id}}

Step 4: Send Web Request – Get Approvers from Golive

This request retrieves Environment Attributes, including the Approvers attribute.

Web request URL:

CODE

https://golive.apwide.net/api/environments/search/paginated?environmentId={{EnvID}}

HTTP method: GET

Headers:

api-key: Generate a Golive API Token and paste it as value.

Important
Enable Delay execution of subsequent rule actions until response is received.

Step 5: Create Variable – Approvers List

Variable name: ApproversList

Smart value:

CODE

{{webResponse.body.environments.attributes.Approvers}}

Step 6: Log Action – Approvers List

Log the raw approvers list to the audit log for troubleshooting and verification.

Step 7: Branch Rule – Iterate Through Approvers

Use Advanced branching to process each approver individually.

Smart value:

CODE

{{ApproversList.split(",").trim()}}

Variable name: Approver

Imporant
Ensure the separator matches the format used in Golive (comma in this example).

Step 8: Log Action – Current Approver

Log each approver value as it is processed.

Step 9: Send Web Request – Resolve Jira User ID

This request resolves the approver name to a Jira user account ID.

Web request URL:

CODE

https://YOUR_JIRA_NAME_HERE.atlassian.net/rest/api/3/user/search?query={{Approver.urlEncode}}&maxResults=1

HTTP method: GET

Headers:

authorization: Basic (Base64-encoded email and API token)

Important
Enable Delay execution of subsequent rule actions until response is received.

Step 10: Create Variable – Approver ID

Variable name: ApproverID

Smart value:

CODE

{{webresponse.body.accountId}}

Step 11: Log Action – Approver ID

Log the resolved Jira user ID for audit and debugging purposes.

Step 12: Edit Work Item – Add Approver

Add the resolved user to the Approvers field.

Use More options and update the custom field ID to match your Jira instance.

You can specify what changes you would like to put into selected fields (e.g. description as in our example) and use ‘More options’ for adding users to ‘Approvers’ field. Make sure to update custom field ID (10003 in our example) to match the ID of ‘Approvers’ field in your Jira instance.

Additional fields:

CODE

{
   "update": {
      "customfield_10003": [
      {
            "add": {"id":"{{ApproverID}}"}
         }
      ]
   }
}

Step 13: Re-fetch Work Item Data

Re-fetch the issue to ensure the Approvers field is updated before evaluating conditions.

Step 14: Condition – Prevent Duplicate Entries

This condition allows multiple approvers to be added while avoiding duplicates.

First value:

CODE

{{issue.customfield_10003}}

Second value:

CODE

{{ApproverID}}

Condition: Does not contain.

Step 15: Edit Work Item – Add Additional Approver

If the condition passes, add the user to the Approvers field again using the same configuration as Step 12.

Use More options for adding users to the Approvers field. Make sure to update Custom Field ID (10003 in our example) to match the ID of Approvers field in your Jira instance.

Additional fields:

CODE

{
   "update": {
      "customfield_10003": [
      {
            "add": {"id":"{{ApproverID}}"}
         }
      ]
   }
}

Step 16: Add Comment to Work Item

Add a comment containing the original approvers list from Golive.

This allows quick verification that all approvers were successfully mapped and added.