Automation close story after release

[Dev]

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

[Jessie Vaught]

Thanks Stefan, this helped me with a similar problem. 

[Stefan Salzl]

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

[Stefan Salzl]

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.

Best
Stefan

[Stefan Salzl]

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.

Best
Stefan

[Stefan Salzl]

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.

Best
Stefan

[Dev]

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?

[Stefan Salzl]

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:

Best
Stefan

[Stefan Salzl]

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?

Best
Stefan

[Dev]

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