Is anyone else having issue with the new release automation template rule to move issues to done?

Ledith_Harrison

I am getting more comfortable with Jira Cloud features and playing around with Release automation templates. 

There is a new one "When new version is released -> move issues to done".  It seems like this would work by just setting the Release to release.  However, a pop up still occurs stating that the issues have to be moved to another Release or updated to done before the Release can be released.  

Seems like with the roll out of the new automation rule, the requirement to have the issues to already set to done before the Release can be release would have become optional in the pop up.  Given that it is not, am I missing some other configuration to set up in order to use the new "When new version is released move issues to done" Release automation rule template? 

I am really looking foward to using the rule if possible.  

Ledith H

Bill Sheboy

Hi @Ledith_Harrison 

Short answer: 

I suspect the pop-up's questions / fields for the Release Version action are meant to help teams decide what to do when there are remaining issues, and the behavior of that automation rule template is independent of that.  Perhaps consider the team's working methods if there are challenges trying to release before the planned work is completed.

 

Longer answer:

I have not used that template rule before, although looking at it, the rule seems simple: on version release, branch to the assigned issues and transition them to "done".

The behavior of automation rules and the UI / UX for Jira are different things, and likely created by different Atlassian teams.  The interactive, user interface is apparently not designed to account for the existence of an automation rule which may alter / supersede the behavior of things like the "Release Version" pop-up. 

And so that pop-up's fields to select the disposition of the issues does not change behavior based on the presence of an active rule.  Doing so would be a challenging problem to solve, as every single rule in the Jira site would need to be examined as there are multiple ways (and scopes) at which the version could be impacted.

When teams do things out of the expected order of their practices, this can be a "smell" of a root cause problem, and reveal opportunities to improve.  A discussion with the team may help to learn a change in practices to help.

Kind regards,
Bill