### Problem to solve Incidents were recently established as a type of issue in GitLab. This provided the opportunity to solve numerous other customer problems that we were limited in solving because we were using Issues in place of dedicated Incidents. This epic is part 1 of a two part effort. Incidents Details - Iteration 2 contains the next scope of work. This epic aims to solve the following problems for a responder of IT Incidents: As an SRE, I want to be able to... - ...investigate metrics and logs in the same interface as my alerts & incidents so that I can discover the root of the problem quickly. - ...review the relevant runbook so that I can restore services for my stakeholders efficiently. - ...publish an incident to my status page before customers learn about the problem to keep stakeholders up to date and bestow confidence in customers for the services they pay for. ### Intended users * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops) ### User experience goal Ensure that people responding to incidents have quick access to all relevant and related content so they can resolve the incident with as little context switching as possible. ### Proposal As part of https://gitlab.com/gitlab-org/gitlab/-/issues/217044, we put together a [sample vision mock](https://gitlab.com/gitlab-org/gitlab/uploads/c513f4db36f124250847a635c9bafd46/Incident.png) for incidents. But, we also hope to align whatever we propose for incidents with the work being done https://gitlab.com/groups/gitlab-org/-/epics/3354. So, the goal would be to modify this vision proposal to fit within the framework established as part of the extensible issues effort. ### WIP Designs | Tab 1 | Tab 2 | Tab 3 | Tab 4 | Tab 5 | New issue type field | Publishing | Related alerts | | ------ | ------ | ------ | ------ | ------ | ------ | ------ | ------ | |  |  |  |  |  |  |  |  | The design files are visible in [Figma](https://www.figma.com/file/EqXIfhBIh9McdO4UHZRf4t/Dedicated-incidents-gitlab-com%26218694?node-id=63%3A342). There is also a simple [clickable prototype](https://www.figma.com/proto/EqXIfhBIh9McdO4UHZRf4t/Dedicated-incidents-gitlab-com%26218694?node-id=63%3A7467&scaling=min-zoom). ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change * Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements * If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references