Phase 1: Introduce incident-specific Slack notifications in the Settings page
Release notes
In 15.8 we're releasing the first iteration of the GitLab Slack App for Incident Management. We want to make it easy for incident response teams to use Slack and GitLab incident management, ensuring Slack-to-GitLab workflows are seamless to minimize repetitive, manual work for incident response teams. With this release you can declare an incident from Slack and set your Slack integration to receive all incident notifications to a specific channel.
https://docs.gitlab.com/ee/operations/incident_management/slack.html
Problem to solve
Right now, Slack notifications for incidents are included within the notification settings for Issues. This means that there is currently no way for incident responders to receive their incident notifications in a separate Slack channel, or for them to define what notifications they would like to receive specifically for incidents.
Proposal
Note: the Slack notifications are currently being integrated into the newly updated GitLab Slack app. So, how our new notification section for incidents will look and where it will be located (either in Settings > Integrations > Slack app or Settings > Integrations > Slack notifications) will depend on where this work is at. The preference would be to wait until the notifications are ported over to the app, though, so that no re-work is required when notifications are ported over. See &8545 (comment 1097603833) for specific context related to this issue.
Introduce a section in the Slack notifications settings page specifically for incidents.
As a first pass, we can start with notifications for when an incident is created. We can build on this initial notification to add notifications for things like status changes, in future.
Note that other incident notifications (updates, closures, etc) can continue to be looped into the general issue
notifications. We're not completely separating out incident notifications at this time, just creating a separate space for incident creation notifications to be sent. Confidential and non-confidential incidents should be treated the same.
There will also be a new notification style for incidents. There will be a separate implementation issue for that work. You can use the standard issue styles for notifications as a first pass.