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

Automation: When issue transitioned link to last created issue from another project

Bodavo

Hello!

I want to automatically link a transitioned issue from Project A, to the last created issue of project B.

This automation rule works in most cases except when there are found multiple issues via "For JQL". Is it possible to apply the "For JQL" only to the first found issue??

Screenshot 2021-06-24 at 16.58.51.png

Accepted answers

Bodavo

The solution is simple and thanks to this post the automation rule has to look like this, to get only the first issue:

Screenshot 2021-06-24 at 17.14.25.png

All comments

Ravi Sagar _Sparxsys_

Hi @Bodavo

Within your branch create a variable and assign it the following smart value.

{{lookupIssues.first.key}}

Make sure you create the same variable before the branch with null value, other wise you won't be able to access it later.

{{lookupIssues}} is the list returned when jql is run within your branch rule.

I hope it helps.

Ravi

Bodavo

The solution is simple and thanks to this post the automation rule has to look like this, to get only the first issue:

Screenshot 2021-06-24 at 17.14.25.png

Bodavo

Thank you!

Bill Sheboy

Hi @Ravi Sagar _Sparxsys_

FYI...I do not believe a created variable will always work in this use case:

It will work when a branch returns one-and-only-one issue, as the branch converts to in-line code
But when there are multiple issues returned, each issue is processed separately and asynchronously; so the created variables within the branch shadow each other, and then go out of scope, leaving the unset variable prior to the branch. There isn't even a guarantee that the branched issue processing will complete prior to the next instruction/component after it.

Please see this post for some spirited conversation on the behavior:

https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Create-variable-New-component/ba-p/1448118#U1450006

Best regards,

Bill

Bill Sheboy

Hi @Bodavo

If you add an ORDER BY statement to your JQL with the Lookup Issues action, that will guarantee that when you use {{lookupIssues.first.key}} it is indeed the latest one. Without the order by clause, there's no guarantee of the return order of the issues.

Best regards,

Bill

Bodavo

Hi @Bill Sheboy thank you for clarification!

Best regards

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud