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; } } }

How to pick a specific fix version when using "Version updated" as a trigger

vincenzo.spatafora

Dear ALL,

I would like to code an automation rule where the trigger is

When: Version updated

My question is: which is the syntax to use under the "More options" of this trigger, called "Version name filter" such that if an issue has for example 2 fix versions, I pick the second one?

I use this expression {{issue.get(1).fixVersions}} but I get "Invalid regular expression".

I use Jira DC version 9.12.

Thanks in advance,

Vincenzo.

Accepted answers

Bill Sheboy

Hi @vincenzo.spatafora

First thing: what problem are you trying to solve? That is, "why do this"? Knowing that will help the community offer better suggestions. Thank you!

Until we know that...

The version-related rule triggers only have the Version: they do not have any issues.

Instead, when you want to access the issues associated the trigger {{version}}, a branch is needed. And, once inside the branch, you could compare the position of the value within either the {{issue.fixVersions}} or {{issue.versions}} values.

Please note well the trigger smart value for {{{version}} is singular to avoid confusing it with the Affects Version smart value, which is plural: {{issue.versions}}

Kind regards,
Bill

All comments

Marc -Devoteam-

Hi @vincenzo.spatafora

Try using:

Bill Sheboy

Hi @vincenzo.spatafora

First thing: what problem are you trying to solve? That is, "why do this"? Knowing that will help the community offer better suggestions. Thank you!

Until we know that...

The version-related rule triggers only have the Version: they do not have any issues.

Please note well the trigger smart value for {{{version}} is singular to avoid confusing it with the Affects Version smart value, which is plural: {{issue.versions}}

Kind regards,
Bill

vincenzo.spatafora

Hi @Marc -Devoteam-

thanks.

And if I would like to take the second one?

I have tried this {{issue.fixVersions.second.name}}) but it gives nothing (and I'm sure there is a second version).

Cheers, V.

vincenzo.spatafora

Hi @Bill Sheboy,

thanks and sorry: yes, I should have explained better.

I got 2 issues which have 2 different fix versions:

when I change the release date of 1 version, the automation rule should update the issue due date to the new release date.

See please below and either I do something wrong or I have come across another Jira DC limitation?

where in editing the due date I use the varaiable being defined earlier on, namely {{NewDueDate}}.

Thanks in advance,

Vincenzo.

Marc -Devoteam-

Hi @vincenzo.spatafora

You could use {{issue.fixVersions.last.name}}

Also see this article from @Bill Sheboy on finding items listed in a field.

https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Dynamic-searches-within-a-list/ba-p/2834235

Bill Sheboy

Thanks for that information, @vincenzo.spatafora

Just to confirm...

Are you trying to update only the issues in the trigger (just updated) version? My assumption is "yes".
Are the Due Dates of the issues always set from a version with some specific naming convention? My assumption is "yes".

If so, you could simplify to this:

trigger: version updated
advanced compare condition (which is called smart values condition in cloud):
- first value: {{version.name}}
- ...somehow check if the trigger version is the one changing the Due Dates
action: create variable, to extract the release date
advanced compare condition:
- check to confirm the new date is valid / not empty
branch: to issues in version
- action: edit issue, setting the Due Date

vincenzo.spatafora

Thanks @Marc -Devoteam- .

vincenzo.spatafora

@Bill Sheboy: may I crown you as the smart person.

Thank You very much: it works.

Kind Regards, Vincenzo.

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-management

jira-service-desk-data-center

jira-service-management-data-center