I can't use 'Execute in bulk' with Jira Cloud, what is the workaround?

[Milan Mainassy]

Hi!

What I want

Send a mail with a list of all the issues at the start of a sprint in 1 e-mail .

What is the current situtation

I can't use 'Execute in bulk' as it seems with Jira Cloud. That's why I use the "Lookup issues" function in combination with JQL: "Epic Link" = INT-10". The issues are now placed as a list in the mail, however the mail receiver still receives the mail times the number of issues.

Can you help me change the mails into 1? :D

[John Funk · Accepted solution]

Hi Milan,

Is this a Next-Gen project? Or a Classic Software Project? 

You might look into use an Automation for Jira rule following the LookUpIssues guidance here:

https://community.atlassian.com/t5/Jira-Software-questions/Sending-an-email-with-a-list-of-issues-using-Automation-for-Jira/qaq-p/1192501

[Milan Mainassy]

Hi John,

It's for a classic Scrum project.

The link that you send me is about doing this via the subscription filter. Are you saying it's impossible to do this via automation?

Thanks!

[John Funk]

Yes, it should be able to be done with Automation. Read down that post to an answer by sreuter with this info:

Subject:

So much goodness, we just released awesome app v{{version}}

Content:

<ul>
{{#lookupIssues}}
<li>{{key}} - {{summary}}</li>
{{/}}
</ul>

[Milan Mainassy]

Yes, and it gives me a great output, but the mail receiver still receives the mail times the number of issues. Which is the issue here.

[John Funk]

If setup probably in your rule, it should only send a single email with the entire list. 

Can you share the rule you have created? 

[Milan Mainassy]

Sure!

• Type of related issues: Issues in the sprint
• Lookup issues: "Epic Link" = INT-10
  
• Send email:  
  

  Hi,

  This is a test.

  <ul>
  {{#lookupIssues}}
  <li>{{key}} - {{summary}}</li>
  {{/}}
  </ul>

  
  Grtz

[John Funk]

Can you show the details of the Send email part?

[Milan Mainassy]

Sure! 

[John Funk]

I think it is because you have a branch in there. Or you have a double lookupissues - one in the branch and another one in the email. 

Try turning the branch into just a condition. 

This is what my test looks like that works:

[Milan Mainassy]

That worked! Thank you so much!

[John Funk]

Glad it worked!