I envision this working in a way where a specific slack channel can receive updates in a chronological manner (every day at 9am) based on a complex JQL filter (such as issues that have been in a certain status for longer than n days). 

I don't believe that is allowed. Should I request this feature?

4473f5bf1aa8, this ticket helps customers who are trying to get notifications for tickets that full under a specific criteria, via JQL search. Today we do not have support for getting notifications that fall under a specific criteria via the Jira cloud for Slack app.

That said, you should be able to achieve this with Automation for Jira- it will let you monitor for specific fields to be changed, and post a message into a specific channel. 

I hope this helps

Trevor

Hi Trev

Any updated documentation on this? We're trying to get notifications sent to a slack channel based on an "when a custom field updates to anything, post in X channel" logic with a filter I set up and having a hard time figuring out how to do this.

This ticket sounds like it addresses that.

Hi, 

Is there any documentation on this that can help us understand the steps for this feature?

Any news here? 

We are trying to create multiple slack channel integrations from the same project based upon a JQL filter that contains a custom field.  It appears that when we can a new slack channel integration, the JQL from the already configured integrations are removed.  I saw some mention of this "limitation" on a https://community.atlassian.com/t5/Jira-questions/How-to-filter-notifications-using-JIRA-Cloud-Slack-integration/qaq-p/679918 that indicated that there is a limitation of one slack channel JQL based integration per project.  I search for any documentation on this but couldn't find anything.  Can you please confirm if there is such a limitation?  If there is, do you plan on changing that?

Hi f716a5cc195d that is not a known issue, do you mind opening a ticket at https://support.atlassian.com/ and we can help look into it? thanks!

I create a JQL filter `(Sprint is not EMPTY) AND (Sprint in (openSprints()))` and then check the "Issues transitioned to <choice>" checkbox, but the filter doesn't apply, and I see the transitions to <choice> of all tickets regardless of the sprint they belong to. 
Is this a known error? 

Thank you, @Trevor, for getting this completed!

I have two suggestions (hopefully you're going to tell me I'm a fool because these already exist or that they're at least part of another issue already:

1. Add global Slack configuration: For example, enter one line of JQL that would cross all projects (just like a normal JQL search can) to do something like notifying a single user via Slack about any issues in which (s)he is mentioned, assigned to, etc.  Currently, it's necessary to enter JQL for each user for each project.  50 users x 50 projects = 2500 lines of JQL instead of only 50!
2. Add more triggers: At least add a very simple one: Issue Edited (whenever anything changes with an issue).  Currently, updates to most fields cannot trigger a Slack notification.

Thanks for adding this feature!

The notification doesn't seem to work if there is a transition screen for a status.

In my project notification, I entered/selected:

I have a transition screen for the Ready for Technical Review step, and did not receive a Slack notification when I transitioned a ticket that matches this notification setting.

However, if I change Issue transitioned to to a status that doesn't have a notification screen, I do receive a Slack notification.