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?

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.

Thanks @Trevor  This is indeed much needed feature.

I need some more info as we have a requirement where we run JQL filter query once a day and send results to a slack channel. Jira allows Slack integration but how to set a daily triggering event in Jira for same?

bryan750998172 That JQL validates just fine, so it should be saving correctly. My guess is that none of the Jira issues match the JQL. Assuming you're trying to catch mentions of you on Jira tickets, it's probably because Jira mentions have a space between your first and last names (see the mention at the beginning of this comment), so nothing matches “BryanGoldberg”. I bet it will work if you change it to the following: 

(summary ~ "Bryan Goldberg" OR description ~ "Bryan Goldberg" OR comment ~ "Bryan Goldberg") and updatedDate >= -7d

I tried the following but couldn't get it work :\

(summary ~ BryanGoldberg OR description ~ BryanGoldberg OR comment ~ BryanGoldberg) and updatedDate >= -7d

🎉🎉🎉 will start using it top of the morning, appreciated!

Hi everyone!

This feature has been released to all users! If you have any issues please report them here  

Form submitted, Trevor - bring on the beta testing as we are dying for this feature!

Hi Trevor. I really need this feature, when is the beta opened?

Hi everyone!

We're looking for some help beta testing this feature. We'd love to include you all so we can hear your feedback and you can help us build an awesome experience!

If you fill out this form, I'll add you to the beta list and you'll hear from me soon  

https://forms.gle/7mfzSRpwbiVJRLVEA

Trevor Thompson

Product Manager, Product Integrations

Do you have an stimated release date?

+1 would love to know ETA

+1 looking for ETA

I love you , all  who updates this issue with so important comments "+1 looking for ETA" - Do you think this is a keyword for Vote for this issue option ? I haven't found this documented
I'm just wondering am I the only person who waits for a real update from Jira team rather then all +1..looking...ETA

+1 looking for ETA

+1 ETA please

It's great that you're working on this - we don't all need to know when small changes are made.

+1 and looking for ETA

Would love to see this feature. Is there an eta on release date?

This would be so helpful for us to map a board to a channel instead of a whole project.  Trevor - keep us updated on timeline! 

would love to be able to map a board to a channel

Hey all! 

I'm putting this ticket to "In Progress" as we've started working on this functionality. Stay tuned for updates via this ticket!

Trevor
Product Manager, Integrations @ Atlassian

Guys, just vote.
Every comment triggers email to all who tracks this issue

Yes, our company would like this also, +1

Is there any status update on this?

+1

+1 want this!

+1

+1

+1 yes, definitely!

+1 to be able to filter by components or JQL

+1 yes, this would be awesome!

+1 yes, please!

+1 I really need it, it generates so much noise it's useless without this feature!

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1 Given that every way of working with jira requires tradeoffs you almost always end up with multiple teams in a project working closely but with separate concerns. Component level filtering would be a massive improvement prior to having more general JQL in my opinion

+1 This would help us a LOT. I believe we all have to turn the notifications off or it becomes way too noisy. Would love if you could filter based on a particular epic and so on

+1 this would be great. Right now sending all ticket updates to the same channel is pretty unwieldy. Some basic filtering would be incredibly useful for toning down all the noise.