Teams Messages - One message for multiple issues

[Devin Ponda]

Anyone know of a way to 'group' MS Teams notifications together when multiple issues are identified in an Automation?

Right now, if more than one issue is identified the automation will send 1 Teams message per each issue identified in the JQL search. I'd like to only have 1 Teams message sent with the list of issues in that 1 notification.

Thanks,

Devin

[Mark Segall]

Hi @Devin Ponda 

I would recommend using an automation like this:

• TRIGGER: Manual or Scheduled
• ACTION: Lookup Issues
  • Your JQL
• ACTION: Send Microsoft Teams Message
  • Message Title: Whatever you want
  • Message:  Something like this...

    {{#lookupIssues}}
    
    * Whatever you want stated for each issue
    
    {{/}}

[Devin Ponda]

Thanks Mark. 

That's pretty much what I have in place, but the way the automations run hits every issue and sends a message for each one.

[Mark Segall]

Hi @Devin Ponda - Right now your JQL is in the Schedule Trigger which means it will iterate over each one.  Instead, you want to set the trigger to just execute without JQL and then use the Lookup Issues action to get your issue results.  From there, you would use the {{#lookupIssues}}{{/}} to group the results.

[Devin Ponda]

I'll look at that again, but I had tried that and was having issues.  I'll let you know what happens.  The error was requiring me to have it in the Schedule Trigger.

[Devin Ponda]

I can't get the IF statement to be there if I remove the JQL from the Schedule and put the Lookup Issue back in. 

I don't want alerts sent if the Lookup finds zero issues, which is what I was going for with the IF statement. 

Error

• The rule has been configured with components that require issues to be provided by the trigger. You need to use the option to run JQL to provide issues. The following components require issues: Issue condition

[Mark Segall]

What if you add this to your Lookup Issues JQL?

AND components IS EMPTY

If there is more to your automation rule, you could add a second up Lookup Issues action later with the clause

AND components IS NOT EMPTY

[Devin Ponda]

Hey Mark!

I appreciate all of your updates and time, I was able to use this by putting in place the following steps.  It's been working as expected so I think we're ok now.