Surface Slack Channel information in issue

Problem to solve

Slack is commonly used for ChatOps during fire-fights. We are leveraging GitLab issues as incidents and currently, users have the ability to configure a project to send different GitLab events (such as creating an issue) to a Slack channel where users will then swarm to resolve it. We want to meet people where they are collaborating and problem solving.

Intended users

Sasha the Software Developer
Devon the DevOps Engineer
Sidney the Systems Administrator

Further details

This work contributes to the Incident Management Vision

Original Proposal

Using the Slack notifications service users can send GitLab events, such as creating an issue, to a Slack Channel. When this service is set up, a user will define a default channel for an event to be sent to if te user does not specify a channel in the service configuration page in GitLab.

Embed a button at the top of the issue underneath the title that users can click to access the Slack channel. We can pull this information from the Slack notifications service settings (see screenshot below). Include the name of the channel in the button.

WIP Proposal

For an MVC, we will utilize the existing Slack notifications service to tie issues to specific slack channels. We've decided to hold off on the pinned embed for the short-term, and will re-evaluate if we need to further elevate the slack channel information in issues down the line.

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

There is an increase users who configure gitlab issues to send to Slack. We can measure this by tracking the number of projects where the Slack notifications service is enabled and the issue trigger box is checked.

Links / references

/label ~feature