Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,942
Community Members
 
Community Events
176
Community Groups

Allow filtering Incident and Scheduled Maintenance Slack notifications by affected components

Currently, Incident and Sched. Maintenance subscriptions for a channel is an all or nothing setting which in our experience has led to having a bunch of channels light up with unread messages when an incident is opened regardless of if the incident is relevant to the channel.

 

Right now, the work around that I have implemented for some of our channels that are component specific is to just turn off incidents for the channel and only leave the component updates for the relevant components enabled. Unfortunately, this doesn't provide the additional context and information that comes with the incident/maintenance notifications.

2 comments

We are also having this problem

Hey @Ricky Grassmuck and @Matt Trachier , welcome to the Community!

It sounds like you're interested in setting up some Slack channels as subscribers to some of the components on your page. In contrast, the built-in integration configured from the admin panel is more all-or-nothing as you've outlined. 

We have a subscription available for Slack in addition to the default subscription options of Email, SMS, RSS, etc. This just needs to be enabled for the page first in the subscription settings:

subscriber-settings-slack

Once it's enabled (and component subscriptions as well), then there will be an option to subscribe via Slack on the Statuspage itself:

statuspage-slack-subscribe.png

And - again assuming you've got component subscriptions enabled - the configuration will let you choose which components to send notifications to the Slack channel to about. Full instructions are available in our support documentation .

Cheers,
Daniel | Atlassian Support

@Daniel Eads Sorry, I should have clarified, this is actually for a private statuspage and not a Public facing one which is a requirement for the options you mentioned.

Daniel Eads Atlassian Team Nov 10, 2021

Ah, thanks for that info. In the case of private pages, you could consider using Webhook Notifications from Statuspage and Slack's incoming webhooks (tied to specific channels).

When you create a webhook subscription from Statuspage, it will send a confirmation email to the address you add along with the webhook URL. The bottom of that email will have a link to manage the subscription:

image.png

On the manage page, you'll be able to de-select components that should not send notifications to the webhook. This still assumes that component-level subscriptions are enabled for the page.

Cheers,
Daniel

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events