Edit Issue Automation - Fix Version

[Scott Roehrenbeck]

I am wanting to automatically set a fix version when a ticket is completed. Our issue, we have multiple types of issues in our project and also multiple releases on our projects (IE a release for mobile, one for web, etc)

I am trying to figure out a way to find the latest unreleased fix version that contains a specific name: IE mobile-release-1.1.1

Is it possible to get all releases and find the first one that contains mobile?

[Trudy Claspill · Accepted solution]

Hello @Scott Roehrenbeck 

Welcome to the community.

I think this post covers the same topic.

(Credit to @Bill Sheboy for his answers on that post.)

[Mikael Sandberg · Accepted solution]

Hi @Scott Roehrenbeck,

Welcome to Atlassian Community!

You would have to use the REST API and Get project versions paginated  to find the unreleased version that correspond to your search criteria, and then use that to set the fix version. JQL can search on versions, but it requires that the issue already have that version set in either Affects version or Fix version.

[Scott Roehrenbeck]

How would you go about using the Rest API within an automation rule?

[Mikael Sandberg]

You can use the Send web request action under Notifications and then use the returned result to get the name.

[Bill Sheboy]

Hi @Scott Roehrenbeck -- Welcome to the Atlassian Community!

Adding to the answers...Here is a how-to article to set up and call a REST API method from an automation rule: 

https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Kind regards,
Bill

[Cloudites Owner]

This automation is usually one step of a broader code repository check-in and release planning set of processes.

When the developer checks in the code they can update comments in Jira from many repositories and using a synced branch naming convention to the fix version, now you have a trigger to fire the fix version automation based on the code repository branch versioning.

This limited example doesn't take into consideration automated testing and release planning cycles which could update your fix version further.