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

Referencing multiple lookups

Jamar Jenkins

Are there any plans to configure an option to reference multiple lookups?

I am working on automation that I would like to use more than multiple JQL lookups in, but it seems that at this time it seems that there is a limitation of 1. I was wondering if something could be implemented where the lookups could get number tags to use multiple?

i.e.:

{{#lookupIssues}}
{{#lookupIssues1}}
{{#lookupIssues2}}

Accepted answers

Bill Sheboy

Hi @Jamar Jenkins -- Welcome to the Atlassian Community!

An interesting idea, and I have not found any open suggestions to add this feature. Perhaps you could add a suggestion with a use case example for your needs.

I recall seeing a post about improving Created Variables to preserve the objects stored in them rather than converting to text. If that happens, there would be no need for multiple lookups: just perform a lookup and store the results in a variable for later use via iterators.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Jamar Jenkins -- Welcome to the Atlassian Community!

An interesting idea, and I have not found any open suggestions to add this feature. Perhaps you could add a suggestion with a use case example for your needs.

Kind regards,
Bill

Jamar Jenkins

So that works. Thank you. Now I just need to figure out how to manipulate the way the information contained in the variables are displayed.

Bill Sheboy

Up to a point, yes.

You could use a Lookup Issues action with JQL to return up to 100 issues, and then use list iterators to parse and store that in a created variable. For example, storing a CSV list of keys or other fields for later use.

Another relatively new feature to reduce the need for multiple lookups is smart value list filtering: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588

With that, you could do one lookup and then filter the list repeatedly to meet your needs. An example use case for that would be to calculate a percentage done for issues in a sprint, epic, etc.

Jamar Jenkins

I think you answered while I was updating my comment. This particular request is completing the desired results. I now just need to figure out how to change this display. When I want to display 1 lookup Key (as URL) | assignee I can use the following:

<a href={{url}}>{{key}}</a> | {{assignee.displayName}}

Not sure how to translate that to the variable(s) though.

Thank you again.

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