You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
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 -- https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828
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.