Slack Automation

[shawn_arline]

We have built an automation WHEN rule that is triggered by conditions of incident priority, or Incident Impact. This then rolls into a slack channel creation automation step that after testing has worked, however we do not seem to have the ability to tell that rule to create a private channel that is owned by the incident management team. 

Is the slack automation rule able to create a private channel instead of a public? If not what are the plans to make this a possibility. 

[Anwesha Pan (TCS)]

Hi @shawn_arline  👋🏼

First of all, welcome to the community! ✨

The short answer to the resolution is to invite the Jira bot into your private channel to allow access. You can follow the below steps : 

1. Homescreen -> Projects -> Select Project that needs to be integrated.
2. Left hand panel, select Project Settings.
3. Left hand panel, scroll down to Slack Integration
4. If any project subscriptions delete ( I did, you can try it out by not deleting)
5. Open slack, go to private channel and type in "/jira connect yourjiraname.atlassian.net". NOTE: You need to integrate JIRA into slack first by signing into JIRA via Slack.
6. Select project, connect. 

You can also use webhook, without specifying the channel in Channel or userfield > as it is defined within the webhook.

Additional resources for this are:

• Use Slack with Automation 
• Integrate Jira Cloud and Slack | Invite the bot to a channel 

[shawn_arline]

Thank you Anwesha, 

We have already set up our Slack integration to work with Jira. The issue we are running into is when we set up the automation to trigger based on the incident specifications we set, the rule does work and will open a new slack channel but the slack channel it opens is public. Once its created we are unable to switch it to private or change the channel name because that is locked behind "ChatOps Admin" rights