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 - update issue with release version

Nick_99p2cx

Hi all,

I hope you can provide some advice for me.

I am using Jira across different platforms (Android and iOS). My user stories are categorized with a component (iOS or Android). I have created two unreleased versions:

[A] 2.1

[iOS] 2.1

Now, I want to set up automation so that when an issue is resolved, the next unreleased release version is automatically added as the fix version to the issue. The challenge is that for Android, it should select the [A] 2.1 version, and for an iOS issue, it should select [iOS] 2.1.

Additionally, I'd like to make it dynamic, so after releasing those versions, when I create two new versions, the automation should automatically pick the new unreleased versions.

This is what I have now:

Do you have any ideas on how to achieve this?

Accepted answers

Kalyan Sattaluri_iinm1n

This requires experts to pitch in. But in the mean time, can you share some more details about your fix version patterns?

- Do you create all your fix versions ahead of time? As in, does your project already have future android & iOS versions in place or will you create a new one only after you have released an existing one? So at any point you only have one unreleased version..

- Do you populate release dates for your fix versions ahead of time or do you populate only at the time of the release? Or do you not populate at all?

Lets assume one of the two below scenarios is true for you:

You create new version only after you have released an old one, so at any time, you only have 1 unreleased version in your project for iOS and android.. OR
Even if you have created future versions, only the latest one has a release date. All other future versions release date is empty.

I think below logic should work:

(btw, Based on the screenshot, I am guessing you are in cloud edition.)

Trigger: Issue Transitions
Condition: if Component/s equals Android
Action: web request call to get your versions pointing to below URL: https://yourdomain.net/rest/api/2/project/yourproject/versions
Advanced branch: Smartvalue = {{webResponse.body}}, variable = {{varIterate}}
Inside Brach, Advanced compare: {{varIterate.name}} contains [A]
Another Advanced compare: {{varIterate.released}} equals false
Another Advanced compare: {{varIterate.releaseDate}} does not equal null
Then, Edit Issue: Fix Versions = {{varIterate.name}}

I havent tried above logic because I am in data center and we dont have advanced branch option but if you have made the API call to fetch your project's version, below thread discusses how to do advanced compare i mentioned..

https://community.atlassian.com/t5/Jira-Service-Management/Automation-loop-through-WebResponse-results/qaq-p/2140920

you could do similar if conditions for iOS component in the same rule.

All comments

Pierre Ibrahim

Hi @Nick

I feel like this can be done in either two branches, or two different automations altogether.

Are you storing the fix versions in two different custom fields (android and iOS)? Or is the triggering issue itself for an Android/iOS and you're just simply copying a value to the fix version from the triggering issue?

Nick_99p2cx

Hi Pierre,

Thanks for your answer!

So what I'm doing is that the story contains the component (Android or iOS).

The automation is triggered by any issue that transitions to a resolved state.

If that is the case, the automation has an if statement that checks if the component is Android. If that is the case, it should be added to [A] 2.1 in this example.

Of course, I can select that version in the automation but then the automation is not future proof when 2.1 is released and you want to work with 2.2.

Kalyan Sattaluri_iinm1n

This requires experts to pitch in. But in the mean time, can you share some more details about your fix version patterns?

- Do you populate release dates for your fix versions ahead of time or do you populate only at the time of the release? Or do you not populate at all?

Lets assume one of the two below scenarios is true for you:

You create new version only after you have released an old one, so at any time, you only have 1 unreleased version in your project for iOS and android.. OR
Even if you have created future versions, only the latest one has a release date. All other future versions release date is empty.

I think below logic should work:

(btw, Based on the screenshot, I am guessing you are in cloud edition.)

Trigger: Issue Transitions
Condition: if Component/s equals Android
Action: web request call to get your versions pointing to below URL: https://yourdomain.net/rest/api/2/project/yourproject/versions
Advanced branch: Smartvalue = {{webResponse.body}}, variable = {{varIterate}}
Inside Brach, Advanced compare: {{varIterate.name}} contains [A]
Another Advanced compare: {{varIterate.released}} equals false
Another Advanced compare: {{varIterate.releaseDate}} does not equal null
Then, Edit Issue: Fix Versions = {{varIterate.name}}

https://community.atlassian.com/t5/Jira-Service-Management/Automation-loop-through-WebResponse-results/qaq-p/2140920

you could do similar if conditions for iOS component in the same rule.

Nick_99p2cx

Hi Kalyan,

Thank you for your detailed answer, very helpful!

To answer your question's first:

Do you create all your fix versions ahead of time? As in, does your project already have future android & iOS versions in place or will you create a new one only after you have released an existing one? So at any point you only have one unreleased version.. -> I only create a new release after I released an existing one. So there is always 1 unreleased Android and 1 unreleased iOS version.
Do you populate release dates for your fix versions ahead of time or do you populate only at the time of the release? Or do you not populate at all? -> Only at the time when I release it. So the release date is empty all time until release.
Yes, it's the cloud edition

So I understand your automation! I tried it but I get a 404 error:

{"errorMessages":["No project could be found with key 'XXX'."],"errors":{}}

Maybe our admin disabled the rest API but I need to check that.

Kalyan Sattaluri_iinm1n

404 error could be because of incorrect URL or credentials.

First lets eliminate URL issue.

Log into your Jira
Open new tab
paste below URL replacing bolded parts

https://yourdomain.net/rest/api/2/project/yourproject/versions

Do you see response?

Kalyan Sattaluri_iinm1n

below is how mine is for FYI

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-cloud