I am trying to create an automation that will send a weekly summary slack. It will contain multiple lookupIssues calls that will have something like this:
New Issues: XX
Open Issues: XX
Closed Issues: XX
Out of SLA: XX
List of issues:
XX-1234 ABCDEF
XX-5678 GHIJKL
Right now I have multiple lookupIssue actions and then multiple Send Message to Slack actions and they all get sent a separate which makes it hard to forward the summary to another slack channel.
Hi @Brandon Leong -- Welcome to the Atlassian Community!
Based upon what you are showing, I can think of two ways to do this:
Better way for rule performance: use one call to Lookup Issues to gather all the relevant issues, and use smart value, list filtering and math functions to report what is needed: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588
For example, to count your completed issues, that would be this:
{{#=}}0{{#lookupIssues}}{{#if(equals(status.statusCategory.name,"Done"))}}+1{{/}}{{/}}{{/}}
How this works:
Better way (maybe) for others to understand the rule: use multiple calls to lookups issues and save the intermediate results in created variables. Then use the variables in your Slack message.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.