---
title: "Golive | Advanced Test Environment & Release Management for Jira"
canonical: "https://help.releasemanagement.app/space/RMC/3393028101/Golive%20%7C%20Advanced%20Test%20Environment%20%26%20Release%20Management%20for%20Jira"
format: markdown
---
> Macro (include)

# Topics

> Macro (toc)

# Overview

Release Management integrates with the [Golive | Environment Management](https://marketplace.atlassian.com/apps/1212239/golive-test-environment-release-management-for-jira?hosting=cloud&tab=overview) 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

- You must be using [Advanced Edition](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3009118209) of Release Management on **Jira Cloud**.
- Ensure that [Golive | Environment Management](https://marketplace.atlassian.com/apps/1212239/golive-test-environment-release-management-for-jira?hosting=cloud&tab=overview) is installed and properly configured.

### 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](media://18243661-5da2-4d97-9628-b2fad956ec15)

- Go to **API Tokens**.
- Create a new token and save it. You’ll need it in **Step 3**.

![image-20250729-142148.png](media://2d18bb6a-cc19-45fb-b9cb-04e7a5544cc6)

![image-20250729-142206.png](media://3afc73cb-6282-4882-99cf-cc9b8ea4e555)

#### 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](media://16bda4d4-28ab-43c4-9d9c-c6a1f0bb2e0c)

#### 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](https://golive.apwide.com/doc/latest/cloud/webhooks).

![image-20250729-142335.png](media://40f4a6eb-ee53-40ec-9eb0-6b2129cd733d)

**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](media://cf0c941a-ed96-4300-9bb4-ae675e122992)

### Requirements

- You must be using [Advanced Edition](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3009118209) of Release Management on **Jira Cloud**.
- Ensure that [Golive | Environment Management](https://marketplace.atlassian.com/apps/1212239/golive-test-environment-release-management-for-jira?hosting=cloud&tab=overview) is installed and properly configured.
- Appropriate permissions to configure **Jira Automation**.

### 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](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2464579589) 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](media://03a80545-41be-4d0b-968c-fde44bd0e74a)

#### 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](media://a3aad277-a597-46d2-96f7-0f53ce23a81f)

**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](media://b466073f-c8d7-4178-bc96-424906b6bbde)

# More reading

Check out respective Golive documentation below:

[https://golive.apwide.com/doc/latest/cloud/release-management-for-jira](https://golive.apwide.com/doc/latest/cloud/release-management-for-jira)  

> Macro (include)