<!-- This issue template can be used as a great starting point for feature requests. The section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. The goal of this template is brevity for quick/smaller iterations. For a more thorough list of considerations for larger features or feature sets, you can leverage the detailed [feature proposal](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md). --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ### Background <!-- What is the user problem you are trying to solve with this issue? --> In https://gitlab.com/gitlab-org/gitlab/-/issues/364422+, we investigated some initial ideas for porting over some of the existing Woodhouse Slack app functionality into the newly updated GitLab Slack App. The goal of this would be to enable a more robust Slack-to-GitLab integration for incident responders. As part of this work, we plan to introduce the following: 1. A place to define Slack notification settings for incidents 1. A way to declare an incident from Slack, and include options to * Add relevant information to the incident from Slack at the time of incident creation (following Woodhouse). * Add appropriate additional resources to the incident at the time of incident creation (zoom link and Slack channel, again following Woodhouse). * Post a notification of incident creation in the appropriate Slack channel, with links to the relevant resources (following Woodhouse). * Post relevant resources that have been added to the incident issue (following Woodhouse). 1. A way to keep content synced up between Slack and GitLab Our goal would be to build on the improved GitLab Slack app the Ecosystem is building. However, if the [notifications haven't yet been ported](https://gitlab.com/gitlab-org/gitlab/-/issues/335673) over to the GitLab Slack app yet, we may need to build on the current GitLab Slack notification integration. More details in [this thread](https://gitlab.com/gitlab-org/gitlab/-/issues/364422#note_1001577223). ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> As part of the discovery issue, we created rough sketches for how introducing these features could look: | Create a space to define incident notification settings | Allow people to create an incident from Slack | Allow for adding data to incidents at the time of incident creation | Post a notification linking to relevant resources in Slack when an incident has been created | Add relevant details from Slack directly to the incident | Find a way to send updates to Slack from GitLab | Refine process for adding Slack comments to incidents | Introduce a way to add items to the timeline from Slack | | ------ | ------ | ------ | ------ | ------ | ------ | ------ | ------ | |  | |  |  |  |  |  |  | **MVC Designs** Through [discussion](https://gitlab.com/gitlab-org/monitor/respond/-/issues/143#note_1091749009) on the technical spike, we've narrowed down the original scope to a MVC. As much as possible, we're aiming to fit within the existing infrastructure, both in GitLab and in Slack. For all designs showing Slack, we should be following the current patterns within the GitLab Slack app. | Introduce incident-specific item to notification settings | New slash command for creating an incident | Slack modal for adding context to incident at the time of incident creation | New incident notification | Incident automatically populated with the content added from Slack | Allow people to send specific comments to Slack from GitLab | Example comment sent to Slack | Make commenting on incidents from Slack easier | Allow people to add to the timeline from Slack | Success/failure message examples | | ------ | ------ | ------ | ------ | ------ | ------ | ------ | ------ | ------ | ------ | |  | | |||| | || | [Click through the designs](https://www.figma.com/proto/yhZmsrVMFJUC390YOKWqUT/Slack-integration-for-incidents-gitlab-com%26364422?node-id=1586%3A36736&scaling=scale-down&page-id=1585%3A36735&starting-point-node-id=1586%3A36736) [Figma file](https://www.figma.com/file/yhZmsrVMFJUC390YOKWqUT/Slack-integration-for-incidents-gitlab-com%26364422?node-id=1585%3A36735) (MVC design tab) [Slack Block Kit Builder](https://app.slack.com/block-kit-builder/) Longer-term, we hope to add more functionality to the incident creation modal, including adding labels and assignees in dropdowns, and adding the ability to create a dedicated Slack channel at the time of incident creation. More details about how that could look are shown [here](https://www.figma.com/file/yhZmsrVMFJUC390YOKWqUT/Slack-integration-for-incidents-gitlab-com%26364422?node-id=1385%3A42269). <!-- ### Intended users --> <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ * [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#cameron-compliance-manager) * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) * [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) * [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops) * [Ingrid (Infrastructure Operator)](https://about.gitlab.com/handbook/product/personas/#ingrid-infrastructure-operator) * [Dakota (Application Development Director)](https://about.gitlab.com/handbook/product/personas/#dakota-application-development-director) * [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst) * [Eddie (Content Editor)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#eddie-content-editor) --> <!-- ### Feature Usage Metrics --> <!-- How are you going to track usage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ --> ### Epic organization & prioritization Issues linked in this epic are named with `Phase <#>`. Within each child epic, items in each phase can be completed in parallel. Between each child epic, blocking issues are accurate. - *Any unblocked* `Phase 1` issue is ready to be worked on & can be done in parallel to any other issue. - If any blocking `Phase 1` issues are completed *within a child epic*, move on to unblocked `Phase 2` issues in that epic, and so on. **Issue dependencies:** | &8805+ | &8806+ | &8808+ | | ------ | ------ | ------ | |  |  | | [Flowcharts source](/uploads/02a8633ae50de2116174266bbe193ced/Slack_App.drawio) --- <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *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.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->