/
Golive | Advanced Test Environment & Release Management for Jira

Golive | Advanced Test Environment & Release Management for Jira

Topics

Overview

Release Management integrates with the Golive | Environment Management to enhance your environment and deployment management. Connect both apps to automate key steps in your release workflow.

Use cases

Real-world examples show how teams use this integration:

  • Trigger Release Transitions (in Release Management) from Golive Deployments

  • Create Golive Environment Bookings on Release Transitions (in Release Management)

Let’s go in details and investigate the use cases ..

Trigger Release Transitions (in Release Management) from Golive Deployments

This integration allows you to automatically move a version to the next stage in your Release Management (RM) board, when a deployment is added to Golive. It helps keep your release tracking accurate and in sync with real deployment events, without manual updates.

Requirements

How it Works

  1. A deployment is added to Golive (either manually or automatically via CI/CD integration).

  2. Golive triggers a Webhook that moves the related version to the next column in the RM board.

Configuration Steps

Step 1: Create your RM App authentication token

  • Open your RM release board.

image-20250729-142105.png

  • Go to API Tokens.

  • Create a new token and save it. You’ll need it in Step 3.

image-20250729-142148.png
image-20250729-142206.png

Step 2: Get the RM Status Transition URL 

  • Open your RM board and select any version.

  • Click the link icon next to the status selector.

  • Choose the target status for the automation and copy the generated link. This link includes the board ID and destination column ID.

image-20250729-142256.png

Step 3: Create a Golive Automation

In Golive, create a new Automation Rule using a Webhook. For more information, refer to the Golive Webhook documentation article.

image-20250729-142335.png

Webhook Configuration

Method: PUT

URL: <https://rmcloud-prd.releasemanagement.app/api/1/board/<YOUR_BOARD_ID>>/version/{{environment.deployment.versionId}}/move?columnId=<YOUR_DESTINATION_COLUMN_ID>

Use the link copied in Step 2, replacing the version ID with the smart value {{environment.deployment.versionId}}.

Example: https://rmcloud-prd.releasemanagement.app/api/1/board/5e4ae23dfc003fehghce2/version/{{environment.deployment.versionId}}/move?columnId=5edfee7afdfdf003fgf6cdc

Headers: X-RM-Token: <your_token_from_step_1>

Custom Payload:

{
"versions":[["{{environment.deployment.versionId}}",true]]
}

Create Golive Environment Bookings on Release Transitions (in Release Management)

This integration allows you to automatically create environment booking requests in Golive when a version is moved on your Release Management (RM) board. It helps ensure environments are reserved at the right time, reducing conflicts and avoiding double bookings.

This guide walks you through the setup in RM and Golive, including the required Jira Automation and Webhook configuration.

How it Works

  1. The release manager sets the release dates in RM version-specific attributes (e.g., UAT Start Date and UAT End Date.)

  2. The release manager transitions the version in the RM board (e.g., from Planning to Development).

  3. A Jira Automation rule creates booking requests in Golive for the related Environments in the different release stages.

image-20250729-142920.png

Requirements

Configuration Steps

Step 1: Create Date Properties for RM Versions

Add custom properties such as:

  • UAT Start Date

  • UAT End Date

Refer to the Custom Properties documentation for setup details.

Step 2: Require Date Entry on Transitions

In the RM board settings, enable the Ask value if empty toggle to require date entry when transitioning a version.

image-20250729-143324.png

Step 3: Set Up Jira Automation for Booking Requests

Create a Jira Automation rule triggered by an Incoming Webhook.

This rule will:

  • Create the corresponding Jira Version, if missing.

  • Create a booking request in Golive.

image-20250729-143416.png

Field Mapping

Start time: {{webhookData.UAT Start Date}}

End time: {{webhookData.UAT End Date}}

Fix versions: {{webhookData.entityName}}

Additional fields: Update with your Golive Custom Field ID and Environment ID.

{
"fields": {
"customfield_13500": ["56"]
}
}

Step 4: Create a RM Automation Rule

Set up an RM Automation to trigger your Jira Automation when a version moves to a board column.

image-20250729-143643.png

More reading

Check out respective Golive documentation below:

https://golive.apwide.com/doc/latest/cloud/release-management-for-jira