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,555,711
Community Members
 
Community Events
184
Community Groups

LookupIssue- Is there a way to have 2 result set in one email

Hi,

I want to use LookIssues to send sprint scope or what is going to get released to my Ops team. 

I was able to accomplish adding two JIRA queries to rule and it works.. but how do I segregate the result in my email

Here is my rule,  what should I add in email so that the output of these two rules is separated

{{#lookupIssues}}
| {{url}} | {{key}} | {{status.name}} | {{issuetype.name}} | {{summary}}
{{/}}

{{#lookupIssues}}
| {{url}} | {{key}} | {{status.name}} | {{issuetype.name}} | {{summary}}
{{/}}

image.png

2 answers

Yes I succeed to do it

1)Create your first jql
2)Record a new variable (with for exemple {{lookupIssues.size}} to have total number of issues
3)Create a second Jql
4)Record again a new variable
5) etc.. repeat operation as needed
6) use your variables in your email


multiple_LookupIssue.PNG

0 votes
Sherry Goyal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 02, 2020 • edited

Hello @Neetu Verma 

 

Thanks for writing to us. 

I am afraid thats now how "lookupIssues" works. Second JQL's output will override first JQL output in variable {{lookupIssues}}

Either

Go for two separate mails, meaning planing rule:
Trigger -> JQL - 1 -> Send email action -> JQL - 2 -> Send another email action

This will shootout two separate emails.

OR

Convert it into one JQL, then you can send one combined email. 

Hope this answers your query. Maybe you can share mode details around your use case, if you seek more assistance.

More details for lookupIssues smart values and article for help.

Cheers
Sherry

Thank you Sherry, I went for on email.  I would like to use this to send all the JIRA tickets which were worked upon in one sprint. 

 

Is there a way I can sort on using Issue types?

Thanks

Neetu

Sherry Goyal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 04, 2020 • edited

@Neetu Verma 

I would suggest to add sorting logic as part of JQL like:

project = ........   ORDER BY issuetype DESC

You can use ASC/DESC and output will probably depend on ordering of issue types in the scheme but default one will work just fine. You can try jql in jira search bar and check the order.

To know more on what all we functions we can do on list using smart values are mentioned here.

 

Thanks
Sherry

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events