Skip to main content
Skip table of contents

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 the approvers defined in the respective Golive environment.

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 user names or user e-mail addresses matching records in Jira as a comma separated value list

  • Admin permissions to create or modify Jira Automation rules

  • A Jira work 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:

  1. Fetches the list of Approvers from Golive

  2. Splits the Approver List into individual values

  3. Resolves each approver to a Jira User ID

  4. Adds each user to the Jira Approvers field

  5. Logs values for traceability

  6. Adds a comment for verification

image-20260401-073208.png

Jira automation example using Golive action


Configuration Steps

Step 1: Define the Trigger

Trigger: Work item created

Configure the rule to trigger on creation of the relevant work type.
You can add additional conditions if required (e.g. narrow down to specific work type).

image-20251211-130303.png

Work item creation as trigger

Step 2: Retrieve the environments properties from Golive

This request retrieves Environment Properties and Attributes for selected environments, including the Approvers attribute.

image-20260401-073710.png

Golive automation action - Get Environments by id

Step 3: Create Variable – Approvers List

image-20260401-073910.png

Create variable

Variable name: ApproversList

Smart value:

CODE
{{fetchedGoliveEnvsbyidList.attributes.Approvers}}

Step 4: Log Action – Approvers List

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

image-20251211-133615.png

Log action

Step 5: Branch Rule – Iterate Through Approvers

Use Advanced branching to process each approver individually.

image-20251211-133745.png

Advanced branching

Smart value:

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

Variable name: Approver

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

Step 6: Log Action – Current Approver

Log each approver value as it is processed.

image-20251211-134032.png

Log action

Step 7: Send Web Request – Resolve Jira User ID

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

image-20251211-134310.png

Web request - Resolve user Jira 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 user email and API token)

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

Step 8: Create Variable – Approver ID

image-20251211-134843.png

Create variable

Variable name: ApproverID

Smart value:

CODE
{{webresponse.body.accountId}}

Step 9: Log Action – Approver ID

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

image-20251211-135032.png

Log action

Step 10: 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.

image-20251211-140550.png

Edit work item

You can specify what changes you would like to put into selected fields (e.g. description as in our example).

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 11: Re-fetch Work Item Data

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

image-20251211-141119.png

Re-fetch work item data

Step 12: Condition – Prevent Duplicate Entries

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

image-20251211-141516.png

Smart values condition

First value:

CODE
{{issue.customfield_10003}}

Condition:
Does not contain

Second value:

CODE
{{ApproverID}}

Step 13: Edit Work Item – Add Additional Approver

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

image-20251211-141822.png

Edit work item

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 14: 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.

image-20251211-142128.png

Comment on work item


Need Assistance?

For support with integrating Golive and Jira Automation, reach out to our Customer Portal.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.