Can I exclude a private project from updating a general slack channel

[tom miller]

We have a high-level project in JIRA that is private to only a handful of concerned users.  Generally, we have all JIRA updates notifying a dedicated Slack channel, and right now, any updates we make to the issues are broadcast to all users.  While the Slack users cannot open the project, they will still see the issue description whenever there is an update.  I am looking for a way to exclude this specific project from notifying slack of activity.  

[Daniel Eads · Accepted solution]

Hi @tom miller ,

If you're using the standard Jira Cloud for Slack app (the one that comes bundled with Jira Cloud), you can adjust the notifications on a per-project basis. This can either be done from the Slack tab in the project's settings, or from Slack itself.

My recommendation would be to start in Slack - in the channel you want to stop notifications from coming in to, use the /jira manage command. This will give you a list of which Jira projects are connected to the channel:

You can use the Manage button there to open the configuration in Jira and make changes. Projects can still be connected to a channel without sending notifications - for example, you can see the first entry in the screenshot has the muted (🔇) icon. This lets you show issue previews if someone mentions an issue key, without sending notifications on changes into the channel.

Hope that helps explain the configuration, let me know if you have further questions!

Cheers,
Daniel

[tom miller]

Great, really appreciate this.  I think, however, that we're configured a bit differently.  When I run the slash command Manage, I receive "There are no Jira projects connected to receive notifications here."  I suspect that, instead, I may need to add a JQL statement to the webhook.  Something on the order of "project NOT IN (proj1,proj2,proj3)" Is this a valid  approach?  I see the current webhook in Jira has no JQL...

[tom miller]

and, thanks again, @Daniel Eads 

[Daniel Eads]

Yes, that's one way to do it. I would suggest not using a webhook entirely though, as the app provides a better interface for making changes. There are security configurations too - using a raw webhook will not check the permissions on an issue (if issue security has been enabled on an issue) before firing a webhook. The actual app configured through /jira manage does however check for issue security before posting an update.

[Daniel Eads]

P.S. - if you do switch from using a global event/webhook in Jira to the native Slack integration, do note that the configurations are per-project. You would need to add subscriptions to each project that you'd like to pipe updates into Slack for. That sounds like what you'd like to do here, but it is a change from what it sounds like you've currently got set up.

[tom miller]

Sounds like a better long-term approach.  Thanks again.