Release Management for Jira

Golive integrates with the Release Management App to enhance your environment and deployment management. By connecting these two apps, you can automate key steps in your deployment and release workflows.

Based on real-world implementations, here are some common use cases:

1. Triggering RM Version transitions from Golive deployments

When the deployment of a version is added to Golive, it can automatically trigger the transition of the corresponding version in the RM board. This ensures that your release tracking in the RM App stays in sync with the actual deployment events occurring in your environments.

How it works

A deployment is added to Golive, automatically via CI/CD integration, or manually.
Golive triggers an update in the RM App, moving the associated RM version to the next stage in the RM board.

Configuration steps

To enable this integration, follow these steps:

1. Ensure both Apps are installed

Golive and Release Management Apps must be installed and configured in your Jira instance.

5. Create a Golive Automation

Create a webhook in Golive, in order to call your Jira Automation when the RM Version transitions to a board column.

PUT

CODE

https://<your-jira-instance>/rest/release-management/1.0/board/<rm-board-id>/version/{{environment.deployment.versionId}}/move

Make sure you replace <your-jira-instance> with your Jira url, and <rm-board-id> with your RM board ID, which can be found on your RM board URL.

Headers

Add an Authorization header with the value Bearer <rm-token> (make sure there is a space between Bearer and the token). For generating a RM token, refer to the RM token documentation.

Custom Payload

CODE

{
  "columnId": <rm-column-id>
}

Make sure you replace <rm-column-id> with the RM board column ID, that can be found by executing GET /board/<board-id> in the RM RestAPI, and referring to the versionColumns sections of the answer.

2. Creating environment bookings on RM Versions transitions

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 defines the release dates in specific attributes of the RM version. For instance, “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 the corresponding booking requests in Golive for booking the related environments in the different release stages.

Release Management Version with UAT dates properties

Configuration steps

To enable this integration, follow these steps:

1. Ensure both Apps are installed

Golive and Release Management Apps must be installed and configured in your Jira instance.

2. Create the date properties for your RM versions

Refer to the Custom Properties documentation article for creating your date properties, for instance “UAT Start Date” and “UAT End Date”.

3. Make the properties mandatory on transition

To ask the user to fill in dates information when transitioning the version, you can use the “Ask value if empty” toggle in your board column settings.

RM board settings to ask for dates when empty

4. Define a Jira Automation to create Golive booking requests

Your Jira Automation, triggered by an incoming webhook, will create the corresponding version if missing in the target Jira project, and create the corresponding booking requests.

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

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

CODE

{{webhookData.versionName}}

Additional fields
(to be updated with your Golive Custom Field ID, and your Golive Environment ID)

CODE

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

5. Create a RM Webhook

Create a webhook in Release Management, in order to call your Jira Automation when the RM Version transitions to a board column.

Webhook configuration in Release Management App,

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.