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

Creating List from JQL Results is failing

Evan Nixon

Hello!

I'm attempting to create a Jira Automation which generates a new issue for me on the first of the month. In the of that issue I'd like the results from a JQL Query in list format. I have no idea what I'm doing wrong here, but oh boy is it frustrating.

I have tried a multitude of things, at this point I've gone back to absolute basics and formatted my new issue's description field to match the format seen here.

The JQL

Rule Settings

Rule Settings.png Rule Settings New Issue.png

Log Results

Log Result.png

Automation Result

Automation Result.png

So with this, a few questions :

Why isn't my {{#lookupissues}} list working/outputting to log?
Why is my {{#issues}} list outputting both keys properly to the log, but only listing a single item in the created issue's description?

Cheers!

Accepted answers

Bill Sheboy

Hi @Evan Nixon

There are a few things to address in your rule to help:

You only wanted one new issue per month (correct?), but your scheduled trigger uses JQL and so that will run for each issue found. Instead please remove the JQL from the trigger.
Lookup Issues' smart values only have information when you first use the Lookup Issues Action. Using the JQL you remove from the trigger, decide what issues you want to gather with the lookup.
You appear to be using Jira Cloud, not Server/Data Center, correct? If so, the {{issues}} (note the plural) is not intended to work with Jira Cloud, and so I would avoid using it. For Server/Data Center, that smart value works with scheduled trigger and branch bulk-processing features.

Kind regards,
Bill

All comments

KJ_dhll5l

The I think you would need the {{#lookupissues}} in the Description and not the log. The log is just to show you info in the audit log.

Bill Sheboy

Hi @Evan Nixon

There are a few things to address in your rule to help:

You only wanted one new issue per month (correct?), but your scheduled trigger uses JQL and so that will run for each issue found. Instead please remove the JQL from the trigger.
Lookup Issues' smart values only have information when you first use the Lookup Issues Action. Using the JQL you remove from the trigger, decide what issues you want to gather with the lookup.
You appear to be using Jira Cloud, not Server/Data Center, correct? If so, the {{issues}} (note the plural) is not intended to work with Jira Cloud, and so I would avoid using it. For Server/Data Center, that smart value works with scheduled trigger and branch bulk-processing features.

Kind regards,
Bill

Evan Nixon

Absolutely - for the intended final output.
In this case I was using the log to debug/display the output of the smart value list.

Evan Nixon

Hi @Bill Sheboy!

Here you are, once again, saving my butt for the 10 Gazillionth time.

I could've sworn that adding JQL to a scheduled trigger was equivalent for {{lookupIssues}}, but right you are that'ss exactly where the solution was.

This :

Makes This :

😎😎😎

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

jql

automation

smart-value