Is it possible to automatically edit the Fix Version field to the most recently created Fix Version?

[Connor Skiro]

Within Jira Automation, I am looking to edit an issue with the most recently created Fix Version. 

My current logic in Jira automation is that when an issue is created, a new Fix Version is created based on the summary text. Then, I'm looking to apply that newly created Fix Version to the newly created issue.

However, my only options when editing the Fix Version field are to select the next unreleased Fix Version.

Is there a way to use smart values with the Fix Version field?

[Yvan Martin · Accepted solution]

Hi there Connor,

Developer from Automation here.

You can actually type in smart fields with most edit fields, it won't be recognised as one until you put in the {{version}} though, see attached screenshot. You should also see other field options such as copying from issue etc.

In general though if you've created a new version, then "Next unreleased version" should already map to the newly created version.

If you require further support with you rule, then you can get in contact with support here: https://support.atlassian.com/

[Connor Skiro]

Hi Yvan, 

Woah, I wasn't aware that you could do this. To me, it wasn't intuitive as the Fix Version field dropdown box made it seem like you had to select one of the options. Thank you for the feedback, your suggestion worked!

> In general though if you've created a new version, then "Next unreleased version" should already map to the newly created version.

I thought this would be the case, however, when I was testing in my sandbox project I found that if there were multiple unreleased versions in the Releases table "Next unreleased version" would always select the version at the most-bottom row. 

In the image below, a newly created ticket would always get tagged with the "Test Release 10110" version instead of "My Test Release 9999".

Nonetheless, thank you very much for replying and ultimately solving my problem!

Best, 

Connor