Jira + Slack: Multiple Notification Conditions
Asked by Katie Pickrell:

Hello! I am working on setting up integrations for my Jira Service Desk with our Slack channels. I noticed that it will not let me setup two different integrations for a single channel so I have a scenario I am looking to see if anyone has advice on.

First let me say, I am aware of the webhook options too but I see that is subject to deprecation so am looking mainly on if the below is feasible in the Slack Connection portion.

I have a single channel and would like Jira to notify the channel for the following 2 scenarios:

- A ticket has a specific label added to it

OR

- A ticket has a comment added when it is in a specific status.

I have the second bullet above configured but can not seem to figure out how to add in the second condition since I can only have a single channel connection based off of a single query. Essentially these are 2 completely different notification scenarios I want notified in the same channel.

Any ideas?


Answers:
author: Callum Carlile
body: Hi [@Katie Pickrell](/t5/user/viewprofilepage/user-id/1353148)

Are you using Jira Cloud or Server/DataCenter? If Cloud, you could create an **automation rule** in the Automation section, where you can select a trigger or Comment Added or Field Updated (and then select the Labels field). You can then add conditions to further restrict when the Slack messages should be sent, and use the Send Slack Message action to send a Slack message to a given channel. Using automation rules over the built-in Slack integration means you can set up as many automation rules as you want to send Slack messages to the same or different channels.

If you are using Jira Server or Data Center, you would need to install [Automation for Jira](https://marketplace.atlassian.com/apps/1215460/automation-for-jira-data-center-and-server?hosting=datacenter&tab=overview) to use the same automation rule functionality, but the setup of the rules would be virtually the same once you've got this add-on

comments: author: Katie Pickrell
body: Hi! We have Jira Cloud. I was just weary of doing that because it said it was legacy functionally that was going to be deprecated so only the new Slack integration itself would be available.


author: Charlie Gavey
body: Hi [@Katie Pickrell](/t5/user/viewprofilepage/user-id/1353148)  

Just to clarify, it's only the legacy automation features which are being deprecated - you can read about this [here](https://community.atlassian.com/t5/Jira-Service-Management/Legacy-automation-is-being-superseded-by-Automation-in-Jira/td-p/1775698).  

The features you can access via "Automation" are fully supported, including the support for Slack:

* g[etting started with automation](https://support.atlassian.com/jira-service-management-cloud/docs/get-started-with-automation/)
* [example templates for Jira / Slack automation rules](https://www.atlassian.com/software/jira/automation-template-library/slack-ms-teams)

Hope this helps!  

Best,

Charlie


author: Katie Pickrell
body: Hi Charlie - So that is where I am at. I go to my Service Desk project, go to Project Settings, select Automation and build a new rule like the one seen below. When I add the Slack option it prompts for a webhook and that page is what indicates the deprecation. Both screenshots are below for reference.

![Screen Shot 2021-11-10 at 2.26.14 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/168839i568E28EA51FA8A55/image-size/large?v=v2&px=999 "Screen Shot 2021-11-10 at 2.26.14 PM.png")![Screen Shot 2021-11-10 at 2.28.13 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/168840iA5C271361199280A/image-size/large?v=v2&px=999 "Screen Shot 2021-11-10 at 2.28.13 PM.png")


author: Charlie Gavey
body: Hi Kate,  

Thanks for confirming! At this stage, webhooks are the best option for implementing automation rules for any use cases that aren't fully supported through the Slack Connection.  

Cheers,  
Charlie


Tags: slack