Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 38,037
    • Issues 38,037
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,345
    • Merge requests 1,345
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #229402

Closed
Open
Created Jul 15, 2020 by Sarah Waldner@sarahwaldner✨Developer0 of 6 tasks completed0/6 tasks

Set severity on incidents

Problem to solve

Severity indicates to responders and stakeholders the impact of an outage. The severity is also frequently used to dictate how a team responds to an incident and the urgency of the response. The value is often correlated to the relative severity of the alert that triggered the incident and needs to be editable so that responders can adjust it as they learn and share findings during the fire-fight.

Intended users

  • Devon (DevOps Engineer)
  • Allison (Application Ops)

User experience goal

Allow users to quickly assess the Severity of the incident issues.

Proposal

Add a new widget to Incidents called severity. It will be a simple selector with values of 1, 2, 3, 4. Locate in the the Side bar.

Default value of Severity when an Incident is created will be based on the severity of the associated alert according to the following table:

Alert Incident
Critical Critical - S1
High High - S2
Medium Medium - S3
Low Low - S4
Error NULL
Info NULL

If the Incident is manually created, the default value will be NULL. A NULL designation will be displayed in the sidebar and on the incident list using the "unknown" severity option.

Design

Severity widget Editing severity
Incidents Incidents-1

Further details

This work supports the Incident Management direction.

Permissions and Security

Documentation

Availability & Testing

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

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Figma file

Release Notes

When you are responding to an incident on the front lines, it is important that you communicate to your stakeholders and team mates the severity of incident as it often determines how they will handle the problem. Moreover, setting severity on an incident helps your incident commander to delegate the right resources and attention to active incidents so that you can address the most critical ones that fastest. The severity of an incident can now be set via the severity widget that appears in the right-hand side bar on Incidents. The severity will also appear in the incident list making it easy to organize active incidents by severity.

image

https://docs.gitlab.com/ee/operations/incident_management/index.html

Edited Sep 01, 2020 by Sarah Waldner
Assignee
Assign to
13.4
Milestone
13.4 (Past due)
Assign milestone
Time tracking