Issue Status Automated Slack Notification

Question

I'd like to create some automations that perform the following:

* Gather counts of issues by issue type and status
* List issues older than X days
* Send a notification to Slack

This will likely require 2 different automation rules, one for the counts and one for listing items older than X days.

I've configured the Slack integration correctly, and message are posted in the slack channel. However, my issue is that the automation basically only sends a line including the status of each issue, and it does so individually. So when this runs, I get hundreds of one-line slack messages with a status, and nothing more.

Has anyone else successfully configured something like this? It seems I'm just setting up the queries incorrectly when attempting to retrieve the counts, or maybe configuring the output message incorrectly.

Piyush Annadate _ACE Pune_ · Answer

Hello @Imperator ,
Welcome to the community !!!

Based on your conditions, all can be done into a single action. Ref for Automation details

1. You JQL can be, older than 90days based on creation, you may change that to updated as well.

type=XYZ and status=SOME_STATUS and created <= -90d

2. With above, you can create a automation as lookup issue component in JIRA Automation:

You actual requirement is mentioned here. 
You can iterate the issue list into a single slack message as below, having KEY, URL

{{#lookupIssues}} 
* <{{url}}|{{key}}>
 {{/}}

For the count, you can use {{issueLookup.size}}  post lookupissue component, provides number of issues that matched the query.  Good to store in an variable and use in your message output.

Bill Sheboy · Answer

Hi @Imperator -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

* what version of Jira are you using: Cloud, Server, or Data Center
* for Cloud, what type of project is this: company-managed, team-managed, JPD, etc.
* an image of your complete automation rule in a single image for continuity
* images of any relevant actions / conditions / branches
* an image of the audit log details showing the rule execution
* explain what is not working as expected and why you believe that to be the case

Until we see those...

From what you describe, this scenario seems possible with one single rule.  However, there are limits to some rule actions:

* you may only gather up to 100 work items (formerly called "issues"), such as to send in a message
* to get counts higher than 100 work items, the REST API is needed

For the symptom you describe sending multiple Slack messages, rather than one message with a list of work items, that is likely because the rule is using JQL in the Scheduled trigger, and so processing each one.  The fix for that is to instead use the Lookup Issues action to gather them to send in one single message using iteration.

Kind regards,
Bill