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

{{lookupissues.size}} returns 0

Marc van Niekerk_8pxdhl

I cannot figure out why {{lookupissues.size}} returns 0 for me.

I have my rule set to manual trigger to test it and then have the following setup.

I know that if I run the JQL query on my ticket (substituting {{issue}} with the actual issue key ,I get 4 results

the log then shows 0 for my {{lookupissues.size}} value:

I am owner of the project and the rule is run using my account. I must be missing something obvious but not sure what

Accepted answers

Marc van Niekerk_8pxdhl

it was the scope. Opening the scope to the other projects that are involved fixed the issue

All comments

Mikael Sandberg

The JQL that you are using is not returning any results and that is why {{lookupIssues.size}} is 0. {{issue}} is not returning the issue key, you need to use {{issue.key}} in order for it to work.

Marc van Niekerk_8pxdhl

I think I might have found an explanation. my linked issues are in another project and i don't think that the lookup likes that

Marc van Niekerk_8pxdhl

it was the scope. Opening the scope to the other projects that are involved fixed the issue

Bill Sheboy

Hi @Mikael Sandberg

FYI...Often for smart values in an expression like this, I think it uses the default attribute when one is not specified; that would be key for an issue.

As the defaults are not documented anywhere, I agree with you that using {{issue.key}} explicitly is better to avoid uncertainty :^)

Kind regards,
Bill

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

jira-software-cloud