How to automate releasing a Release

[Conrad Goodman]

I need to set up an automation rule to release a 'Release' within a project, when the condition is met that all tasks tagged with that version are in the status of 'Released'.

I have seen there are various options for releases in Automation, including 'When Version Unreleased'.

I've tried Google and ChatGPT, but I'm a complete beginner and cannot make sense of the answers.

[Mark Segall · Accepted solution]

Hi @Conrad Goodman and welcome to the community!

At a basic level, you could do something like this:

• TRIGGER: Issue Transitioned (To Released)
• ACTION: Lookup Issues
  • fixVersion IN {{issue.fixVersion}} AND status != Released
• CONDITION (Advanced)
  • {{lookupIssues.size}}
  • Less Than
  • 1
• ACTION: Release Version

However, this would require more complexity if you're tagging issues with multiple versions (e.g. issue gets simultaneously tagged to major release for planning purposes and minor release for CI/CD purposes).

[Conrad Goodman]

Thanks for the help, I have set this up but I'm not confidnt in enabling it, as I don't fully understand the steps.

TRIGGER is obvious, a sub-task is transitioned to released.

ACTION the logic looks like if any fix version of any description exists, and the status within the issue is set to released... Not sure if this looks up all the issues associated with the version of the issue that was transitioned in the trigger step?

CONDITION the logic appears to look for zero issues? Is this zero issues, not sure I understand this.

Action: Release version.. Can i put something in so it only releases the version that is tagged in the release? I can only see an option for release the next unreleased version, but I want it to release whatever version was tagged in the issue that was transitioned, if it was the last one tagged in the release.

We don't tag issues with multiple versions, so hoping this will suffice! Thanks a lot.

[Mark Segall]

Here's a breakdown of the steps:

1. Issue Transitioned to Release
   Correct - This is just how it fires
2. Lookup Issues
   This is looking for any issues that share the same fixVersion and status is not yet Released
3. Condition
   Makes sure that the Lookup Issues action above returned 0 issues, ensuring that ALL tasks sharing that fixVersion do in fact have a status of Released
4. Release Version
   Releases the version

[Conrad Goodman]

Thanks a lot Mark. Step 4 is the only one I'm still unsure on. From JIRA:

---

By default, this will release the next unreleased version with the existing release date. If none is set, release date will default to today. You can change the order of the next unreleased version in the 'Releases' screen of the project and change the other options in the 'More options' section below.

---

Will the above automation only release the version that the intial issue was assigned to in fix versions?

It is unclear to me, what happens in the scenario that perhaps we have 2 unreleased versions of differing project names like 230402-Sales and 230402-Operations for example...?

Cheers

Conrad

[Mark Segall]

You could get more specific with which version to release by using this smart value:

{{issue.fixVersions.Name}}

This will specifically release whatever fixVersion has been applied to the issue that triggered the  rule.

[Conrad Goodman]

That is a perfect solution, cheers Mark!!