Troubleshooting?

Topics

Introduction

Release date is not a required field for packages and could be missed. Sametime you might want to autofill it when it comes to terminal state.

The below example show how to execute it with Release Automation Explained

Step 1: Create Release Automation rule

Open Release Automation and click Create.

Define some name for your rule and select “Package“ for rule scope.

Add “Package Moved“ trigger.

Open

Add field condition to execute the rule at the terminal step only.

Open

Step 2: Get base64 API token

Execute Step 1 and Step 2 Swagger: Rest API & Integrations | How I can get a JWT token to access API? to get BASE64 encoded token (NOTE: the token could be decrypted back so please use system account credentials with limited access scope)

Step 3: Add first Hook (get JWT Token)

Add action “Execute Webhook“.

Fill in the following data:

• Description: Get JWT Token

• Method GET

• URL:_https://YOUR_JIRA_INSTANCE.atlassian.net/plugins/servlet/ac/app.releasemanagement.rmcloud/board?classifier=json

• Body: Empty

Open Headers tab and add header

• Key: Authorization

• Value: BASIC BASE64 encoded token

Save webhook

Step 4: Add second Hook (set Release date)

Create a new webhook that will follow the previous one

• Name: Set Package Date

• Method PUT

• URL: https://rmcloud-prd.releasemanagement.app/api/1/package/{{entity.id}}

• Body: {"releaseDate":"{{date.now(0,'yyyy-MM-dd','GMT+0')}}"}

Open Headers and add header

• Key: Authorization

• Value: JWT {{prevWebhookData.body.contextJWT}}

Save the webhook

Save the rule

Step 5: Execute and test it!

Test it by moving the package to the defined status.

Check the execution result in the webhook history.