Phase 1: Add `/slack <channel>` quick action to GitLab to post incident updates
Release notes
Problem to solve
Since we've heard from testing sessions that content shouldn't be automatically synced between Slack and the GitLab incident (most particularly as discussions in Slack might be confidential and shouldn't be automatically posted to what might be a public incident), we need to give people a quick way to send content back and forth between Slack and GitLab.
Phase 1: Add `/gitlab incident comment <text>` ... (#374957) will handle sending comments from Slack --> GitLab. This issue will be about sending content from GitLab --> Slack.
Proposal
Introduce a slash command in GitLab to send comments to a designated channel in Slack.
Slash command | Example comment sent to Slack |
---|---|
![]() |
![]() |
As noted in the design, people could designate the Slack channel as part of their slash command. If they don't designate a channel, and the slash command is used, we would send the comment to: 1) the slack channel attached to the incident in the Linked resources
widget (if one has been attached); if there is no slack channel attached to the incident, but there is a general channel associated with incidents in Settings > Integrations > Slack > Incidents, we can use that channel; if there is no channel in Settings, either, the slash command would fail. If multiple channels are linked to the incident, we should send the comment to all of them.
Intended Users
Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.