Trigger RM Version Transitions from Golive Deployments

Make sure your Jira releases stays in sync: trigger a transition in the Release Management boards when adding a deployed version to a Golive envrionment.

When you add a deployed version to a Golive environment, it can 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:

Step 1: Install and Configure Both Apps

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

Step 2: Create a Golive Automation

Set up a webhook in Golive to trigger Jira Automation when an RM version transitions.

Webhook Configuration

PUT

CODE

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

Replace <your-jira-instance> with your Jira URL, and <rm-board-id> with your RM board ID, found on your RM board URL.

Headers

Add an Authorization header with the value Bearer <rm-token> . Ensure 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>
}

Replace the <rm-column-id> with the RM board column ID, which can be found by running GET /board/<board-id> in the RM RestAPI. Locate the versionColumns section in the API response.

Questions?

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