nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Automation - How to "release" a fixed version a day after set Release Date and other question

unknown

New to automation and I'm struggling to understand so please bare with me.

Scenario 1: I'm attempting to set up automation so that the fixed version is "released" the day after the set Release Date.

Scenario 2: If that can't be done, how to automate to have the fixed version released on the Release Date.

Scenario 3: I have run into an issue in the past when I manually release a version and that's when not all items are in 'Done' state which prompts me to consider those items and what to do with them. Is there a way to automate an email if not all items linked to the version are in 'done' state for the version to be released?

Accepted answers

Bill Sheboy

Hi @[deleted]

The answers to your questions are: yes, yes, and yes; those are possible with automation rules.

The details depend upon whether or not your releases (i.e. versions) *always* have issues assigned.

For example with scenarios # 1 or 2, you could use a scheduled rule (without JQL) and an action of Lookup Issues (with JQL) to find issues in the earliestUnreleasedVersion() and then check the date of the version to decide what to do, such as release the version with another action.

Similarly for scenario # 3, you could check the issues (as found in the Lookup Issues above) to consider their status, and then report them. For this one, smart value list filtering could help if you only want to make one, not multiple Lookup Issues calls, before checking for email sending.

Now if your releases may be empty (no issues assigned) the above approaches will not work. Instead you would need to use the REST API to find any versions by using a web request from the rule .

Kind regards,
Bill

All comments

Bill Sheboy

Hi @[deleted]

The answers to your questions are: yes, yes, and yes; those are possible with automation rules.

The details depend upon whether or not your releases (i.e. versions) *always* have issues assigned.

Now if your releases may be empty (no issues assigned) the above approaches will not work. Instead you would need to use the REST API to find any versions by using a web request from the rule .

Kind regards,
Bill

Stefan Salzl

great suggestion @Bill Sheboy ....

only want to add a detail to earliestReleasesVersion() —> I once answered a question here dealing with earliestReleasedVersion() didn‘t deliver the correct result. As the description field in the docu tells this function refers to the order of your versions. This could possibly lead to confusing results.

Best
Stefan

Bill Sheboy

Thanks for the reminder, Stefan! Indeed the order of versions in the releases/versions list is what Jira uses as "next" and "earliest". That seems to have been a design work-around as the release date fields are not required. :^)

Abirami Dhanush

@Bill Sheboy thanks, but is there a way I could get all the unreleasedversion with today's releasedate?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

automation

release