Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


{{lookupissues.size}} returns 0

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:log.png


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

3 answers

1 accepted

2 votes
Answer accepted

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

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

0 votes
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 06, 2023

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.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 06, 2023

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,

Like Mikael Sandberg likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events