Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation: Assign issue to next unreleased fix version not updating the field

I've got an automation that runs when any issue is marked as Done, and updates the Fix version to the next unreleased version. It has been working well for a few weeks, but it seems to have stopped updating the field about 2 weeks ago

When I check the logs, it says that the automation ran successfully, but then when I look at the issue the fix version is still blank. As a test, I edited the automation to update issues to a specific fix version and that was working.

Any ideas what could have changed that stopped this working?

1 answer

1 accepted

1 vote
Answer accepted
John Funk Community Leader Feb 08, 2021

Hi Robbie,

There is a known bug that has popped up for this.

You can follow here:

I believe this has now been fixed and deployed. @Robbie James

Yes, I can confirm it appears to be working now, thanks!

Like John Funk likes this


This error also affects the server version of the plugin but i see only a fix for the cloud version. Is there a fix for the server coming?


as far as I know this bug affects server version when issue is cloned and we have fix for that ready to be released with 7.2.9.

I haven't observed that edit issue action is affected.



yes this is correct. This affected the server version of the plugin in the use case where an issue is cloned and the "next unreleased version" is used.

Glad to hear that this is being fixed with the next release.

kind regards,


Follow up question: When will the release 7.2.9 be available?

Next release is planed in the middle of April.



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events