JIRA Automation on Releases

[Nitin Gupte]

Please send me any documentation that can help me create a rule to send email when I add an approver for the Release.

[Bill Sheboy]

Hi @Nitin Gupte 

You could use the issue field changed trigger to start your rule, and then send the email.

To get you started on creating your rule, please refer to these documentation and example sources: 

• https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation
• https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC
• https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

Kind regards,
Bill

[Nitin Gupte]

Thanks for responding Bill, am specifically looking for examples on the Releases screen.

[Bill Sheboy]

Thanks for clarifying that!

When the approvers change for a version, that does not appear to raise an event that can trigger an automation rule.

As a work-around, a scheduled trigger could be used to check a specific version, using a REST API function, as that can see the approvers and their status of approval:

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-id-get

An example rule to check the approval status of the next unreleased version would be

• trigger: scheduled
• action: lookup issues with JQL to gather issue for the next unreleased version
• action: Send Web Request, to call the REST API function, using this as the version id: {{lookupIssues.first.fixVersion.id}}
• action or condition to parse the response

In the call to the REST API function, remember to add this to get the approvers:

?expand=approvers