Have issues running Release Automation rules? Please check our troubleshooting guide - https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033/Release+Automation+Explained#%F0%9F%86%98-Troubleshooting-Automation-Rules.
Topics
Introduction
In Release Management App we allow to send Slack/Teams notifications upon release change via Release Automation Explained. We do not support “Sending Emails“ as possible actions, but Jira does. Therefore, it’s possible to create an automation rule with outcoming hook so Jira Automation receives a payload and construct the message you want to send.
Let’s see how we can do it.
Step 1: Create Jira Automation rule
Navigate to Automation in Jira and create a rule.
Select Incoming webhook as trigger.
Copy Webhook URL, you would need it in Release Management.
Select “No issues from the webhook“.
Add “Send email“ as action.
Put some temporary Subj and Body for now. We will come to it later.
Click Save.
Step 2: Create Release Automation rule
Click Settings on your Release board and select Automation.
Add new rule.
Give it some Name.
Select Scope - Version or Package
Click on Triggers and decide when you want to fire up and email. For the sake of example let’s select version move (=status change).
Add condition if you want to fire email only if the version move to a specific column(s).
Add “Execute WebHook“ as Action.
Give it some description.
Copy the URL from Jira Automation (URL from incoming webhook action in Jira Automation rule).
Define Payload that want to stansfer via the hook. In other words version/package properties you would need to compose a message for your recipients.
The format of the payload is JSON. You can use any available JSON validator to verify the correctness of the data.
{
"data": {
"updatedVersionName": "{{http://entity.name }}",
"updatedVersionStatus": "{{changedProperty.newValue}}",
"versionURL": "{{entity.link}}"
}
}
You are free to call the parameters in the data collection the way you want so it’s easier for you compose a message on the later stages.
As values you can either hardcode smth in the payload or use some dynamic values from https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033/Release+Automation+Explained#Injectable-variables.
Click Save & Save.
Step 3: Compose the message and turn on
Now let’s get back to Jira Automation rule an open it for Edit.
You can now use the data passed from Release Management to update the Subject and the Body the way you like, for e.g.
Subject
Version {{webhookData.updatedVersionName}} changed
Body
Hi there,
We would like to notify you that version {{webhookData.updatedVersionName}} was moved to {{webhookData.updatedVersionStatus}} status.
For more details: {{webhookData.versionURL}}
Kind regards,
Release Management Team
Turn on the rule.
Step 4: Troubleshooting automation
If you are triggering the action but not necessarily see the expected output (e.g. email being sent)
1st Navigate to Release Automation rule
Click on History. Check the last item and select “Show more“.
Scroll to see any reason if the status is Failed to help you troubleshoot.
2nd Navigate to Jira Automation
Click on Audit log. Get the latest relevant item and select “Show more“.
Scroll to investigate the issue if status is “Some Errors“.
Tip: Still have questions or need hands-on advice?