| Table of Contents |
|---|
Generic use cases
...
Create a milestone when issue of specific “issueType” is create/attached to version
Assign environment when version is released / Epic moved to a specific column
Achieve milestone when the issue is done / Version is released
We suggest to use Automation via Outcoming WebHooks to run Automation in Jira as post action in Release Management or use our Swagger: Rest API & Integrations to execute some actions in Release Management in scope of Jira Automation rule.
...
Header: <Name: Authorization, Value: Bearer Your Personalized Token>
Method: <PUT>
...
Let’s check the audit log of the rule.
...
Enjoy it!
⬅️ Create Release in Release Management and assign a Tag
This is the use case of creating Release, putting it in specific Column and assigning Tag to it. Why it’s important? - It shows how you can create multiple actions with Jira Automation and connect execution of one action with another.
Step 1: Get Prerequisites in place
From previous example you know how to:
Step 2: Create Release with Jira Automation
Go to your Project Settings, select Automation and Create rule.
Select the Trigger and Conditions you need
Add Send Web Request action
...
Add the following parameters:
URL: <https://your_jira_url/rest/release-management/1.0/release>
Header: <Name: Authorization, Value: Bearer Your Personalized Token>
Method: <POST>
Request Body:
| Code Block | ||
|---|---|---|
| ||
{
"name": "Release for: {{issue.summary}}",
"description": "Release Description Description",
"versionIds": [],
"virtualVersionIds": [],
"columnId": your_column_id,
"boardId": your_board_id,
"startDate": "2023-11-01",
"releaseDate": "2023-11-30"
} |
Please make sure you specify empty versionIds and virtualVersionIds arrays. Otherwise you get the following response with error:
{ "errorMessages": [], "errors": { "versionIds or virtualVersionIds": "Required field" } }
...
| Info |
|---|
IMPORTANT: Make sure that “Delay execution of subsequent rule actions until we've received a response for this webhook“ is enabled for release creation webhook. This will allow to create subsequent actions to assign additional properties to release for e.g. Add Comment, Assign Tag, Add Milestones, etc.) |
Step 3: Add subsequent action (e.g. to Assign Tag to Release)
Create another Webhook action
...
Add the following parameters:
URL: https://your_jira_url/rest/release-management/1.0/tag/release/{{webhookResponse.body.id}}
| Info |
|---|
webhookResponse.body.id is the ID of Release you created on previous step. |
Header: <Name: Authorization, Value: Bearer Your Personalized Token>
Method: <PUT>
Request Body: Array
| Code Block | ||
|---|---|---|
| ||
["MyTag","AnotherMyTag"] |
| Info |
|---|
IMPORTANT: make sure that tags don’t have any spaces inside. “AnotherMyTag“ - OK; “Another My Tag“ - is NOT OK |
Save the step and the whole rule.
Test it and make sure that the execution status is Green.