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!


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 close story after release

Hi there,

I'm trying to use automation to move a story from "Done" to "Close" once a release Version is release. We are maintaining multiple Projects with different versions.

Unfortunately, I'm getting an error and I'm unable to find the solution.

Thanks for the help in advance


2 answers

Thanks Stefan, this helped me with a similar problem. 

Stefan Salzl Community Leader Aug 03, 2022

It‘s my pleasure. Good to know it was helpful 🥳👌🏼

1 vote
Stefan Salzl Community Leader Mar 09, 2022

Hi @Dev 

As the "Version" is the trigger of your automation rule all the following steps refer to this entity. So in this case the automation rule would ask for the status "Done" for the version and then try to transition the version/release to status "Closed" (which is not possible as version is not an issue type)

The rule needs to collect issues (stories) with the fixedVersion from the trigger. This could be done with rather

  • lookupIssues or
  • branch with jql

and then transition those collected issues to "Closed".

Hope this helps. Please let me know if you have any further questions.


Hi @Dev 

There is even a branch for "issues fixed in version" 


this will collect issues for the version that triggered the automation rule without any lookupIssues or JQL 🙌
You could also set a condition there for only closing issue type "Story" and then add the transition action within this branch.


Stefan Salzl Community Leader Mar 13, 2022

Hi @Dev ,

Did this solve your problem? If so please consider to click "Accept" in order to mark this post as solved.

Thanks in advance.


Unfortunately it didn't. I'm not using branches and I did not see where I can add

"lookupIssues" in it. Do you have maybe an example?

Using a branch is more performant than a lookupIssue action (which is unnecessary anyways with a branch). A good practice is to "keep it simple" ;)

The following simple rule should do the work:



Like # people like this
Stefan Salzl Community Leader Mar 17, 2022

Maybe you have to delete your trigger and re-create it. I´ve experienced some hickups with some triggers after changing the rule/not executing a jql within the trigger.

Could you try the suggested approach meanwhile?


Thank you very much for your reply. The automation rule seems to be fine. I don't have a safe playground to close a version now. So I will test this and let everyone know if this works well. But for a first glance, it looks good!


Thank you

Like Stefan Salzl likes this

Suggest an answer

Log in or Sign up to answer