Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Automation: Release is approved.


I'm trying to figure out if there is any automation options to release a version when it becomes approved?  The approval condition in the automation only says it works for jira service management?

It would be good to be able to initiate the release upon approval.

2 answers

1 accepted

0 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 10, 2023 • edited Nov 12, 2023

Hi @David McCorkindale 

While there is no automation rule trigger for approving a release, and the Version Updated  trigger does not detect approval changes...there is a work-around: use a scheduled trigger and call a REST API function to check approvals.

For example:

  • trigger: scheduled trigger rule
  • the fuzzy part...decide which versions to check, or check them all
  • action: Send Web Request to call a REST API function to get the information (please links below)
  • advanced compare condition: check if your version is approved by all approvers
  • action: release version

Regarding the fuzzy part, to use a specific version, you could use Lookup Issues with JQL to find the issues in the next, unreleased version...and then use that in a call to the REST API.  This seems a better idea than...Or, you could gather all of the versions and parse / filter them.  That may be a problem later as more versions are added, pagination or filtering is required to get your correct version.

When making the REST API call, add the following to the end of the URL so the approver information is returned:



If you want to try this approach, here are some references:

How-to article for calling the Jira REST API from a rule --

Get a specific version --

Get all versions, paginated --


Kind regards,

0 votes
Valerie Knapp
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 10, 2023

Hi @David McCorkindale , thanks for your question.

You could try, as a workaround, if you use an issue in Jira to record when the Release is approved, on the transition to the status to 'Approved' to release the version, like this


The default behaviour of the rule is to release the next unreleased version but it should be possible, if you have the FixVersion in the Jira issue, to refer to that with a smart value.

Please evalaute this solution and give us your feedback.


Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events