Create Environment Bookings on RM Versions Transitions

Prevent environment booking conflicts: automatically create Golive environment booking requests when a version is moved in the Release Management board.

When a version is moved in the RM board, Golive can automatically create environment booking requests to ensure resources are allocated for upcoming deployment activities, and preventing environment booking conflicts.

How it Works

The release manager sets the release dates in RM version specific attributes. For example, “UAT Start Date” and “UAT End Date”.
The release manager transitions the version in the RM board (e.g., from "Planning" to "Development").
Jira Automation creates booking requests in Golive for the related environments in the different release stages.

Release Management Version with UAT dates properties

Configuration Steps

To enable this integration, follow these steps:

Step 1: Install and Configure Both Apps

Ensure Golive and Release Management Apps are installed and configured in your Jira instance.

Step 2: Create Date Properties for RM Versions

Define properties such as "UAT Start Date" and "UAT End Date." Refer to the Custom Properties documentation for setup details.

Step 3: Require Date Entry on Transitions

Use the Ask value if empty toggle in RM board settings to prompt users to enter dates when transitioning a version.

RM board settings to ask for dates when empty

Step 4: 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.
Generate a booking request in Golive.

The rule trigger is an “Incoming webhook”

The “Create version” action creates the Jira version, in case it does not already exist in the Jira project

The “Create issue” action creates a Jira ticket

Field Mapping

Start time

CODE

{{webhookData.bookingStartDate.toDate("yyyy.MM.dd HH:mm")}}

End time

CODE

{{webhookData.bookingEndDate.toDate("yyyy.MM.dd HH:mm")}}

Fix Version/s

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

CODE

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

Step 5: Create a RM Webhook

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

Webhook Configuration

POST

Get this URL in the Trigger step of the Jira Automation you have created.

Body

CODE

{"data": {"bookingStartDate":"{{version.UAT Start Date.formatDate('yyyy.MM.dd HH:mm','GMT')}}", "bookingEndDate":"{{version.UAT End Date.formatDate('yyyy.MM.dd HH:mm','GMT')}}", "versionName":"{{entity.name}}"}}

Webhook configuration in Release Management App, Headers tab

Questions?

If you need help with your Golive-Release Management integration, feel free to contact us.