Auto release multiple issues in a project

Question

I have an automation rule to create a release version and then release it and mark the issues/tickets and done and resolved. What happens is if multiple issues are in the release, the first time the rule runs it goes fine but then it runs and fails for all the other issues because the version name already exists

is there a better way to do this?

Kevin McGillicuddy · Answer

OK I think I have a fix in place now - will come back to this if this does not work as we hit other workloads but new layout is this:

With the "edit issue field - Fix Version" using the fix version for the next unreleased version

Bill Sheboy · Answer

Thanks for clarifying that!

If your goal is to have the 4 issues (with different branches) in the single Jira version/release, please take a look at those subsequent firings to see if there is information in the trigger message that can be used to ignore the version creation steps in the rule.

If instead your goal is to have each issue in a separate Jira version/release, you would need to modify the version create in a manner which makes its name unique, as you cannot rely on date/time {{now}} without using the millisecond format.

Otherwise, there may be a defect in here, and I recommend that you submit a support ticket to Atlassian to see what they say about that trigger.  You should be able to do that as site admin for a paid instance here: https://support.atlassian.com/contact/#/

Once you hear back from support, please post what you learn so the entire community can benefit.  Thanks!

Kevin McGillicuddy · Answer

oh no so when deployment status changed is a trigger - since we have bitbucket, when the issue linked to the branch sees the pipeline deployed to Prod it triggers this rule

I believe its the former.. since each issue is its own Jira ticket with its own bitbucket branch but as I said its strange on first run it gets all 4 issues in the first release, which is reight and then fires empty and so fast it makes these empty duplicate releases which never actually get created (since they would in theory sit in a unreleased state)