<!-- 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). " --> ### Problem to solve When there is an ongoing incident, companies need to organize themselves in order to respond to it. Some of these activities may include but are not limited to paging the on-call engineer if not done already, assigning specific incident roles, capturing initial known information regarding the incident, starting an incident issue, starting a slack channel, starting a zoom meeting, kicking off other types of automation, creating a freeze window, putting up a broadcast message to all of the developers, etc. The exact set of activities can differ by organization, teams within the same organization, severity of the incident, the type of incident etc. We should enable an easy way to automate as many of these manual tasks as possible while enabling teams the flexibility to choose the automation that's actually required. ### Proposal #### Iteration 1 The MVC to solve this problem may already exist. Incident issues can take advantage of templates and quick actions to automate some tasks. #### Iteration 2 Ship GitLab with (a few?) templates that take advantage of existing functionalities. Even if people don't use them, it serves as good documentation in the product. Default to the most common template. #### Iteration 3 Allow custom quick actions that aggregate other quick actions. This becomes "runbooks" #### Iteration 4 & beyond - Add UI, people can point, click, drag to create these custom quick actions - API access, so we can enable things like slack integration and other integrations ### Intended users Incident responders Though I am guessing this has utility outside of incidents ### 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 --> Based on the proposal, we could measure the following: 1. Incidents created with templates 2. Incidents using quick actions 3. Number of custom quick actions created 4. Users creating custom quick actions 5. Users using custom quick actions <!-- 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/ --> <!-- 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 -->