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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,670
Community Members
 
Community Events
184
Community Groups

#lookupIssues not returning any values

 

@Bill Sheboy 

Use case : For each reporter , all the issues he has created without mandatory tags a consolidated email needs to be sent with jira links of all the issues. 

Using issue.toUrl simply sends one email per issue ( ex 5 emails for 5 issues ) & #lookupIssues is sending emails with blank body. Below are the screenshots : 

 

20230330_232014-min.jpg20230330_232025-min.jpg20230330_232043-min.jpg

1 answer

1 accepted

0 votes
Answer accepted
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.
Apr 03, 2023

Hi @Kunal Kumar 

To use the {{lookupIssues}} smart value, you need to first call the Lookup Issues action.  Please try this change to your rule:

  • trigger: scheduled with no JQL
  • action: lookup issues with the JQL you previously had in the trigger
  • action: send your email

Kind regards,
Bill

Get it , but I am on JIRA server and lookup issue action is not available for me to use. Is there any other way I can achieve this use case ? 

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.
Apr 04, 2023

Thanks for clarifying, as your post indicated you were using Cloud but you are actually using Server/Data Center.

The Server/Data Center version has an option for bulk-issue processing.  This is a setting you select either with the Scheduled Trigger with JQL or with a Branch.  After enabling the setting, you would use the {{issues}} rather than the {{lookupIssues}} smart value.  https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html

You can use your original rule with JQL in the scheduled trigger, enable bulk processing, and replace {{lookupIssues}} references to {{issues}}  Please note that is plural {{issues}} for bulk-issue handling.

Thank you so much @Bill Sheboy Worked like a charm

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events