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
  • #230847

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

Surface alert fields in a tab on Incidents

Problem to solve

The alert payload contains critical information to solving an outage. This information needs to be easily accessible on Incidents so that the response team does not have to switch tools and waste time.

Intended users

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

User experience goal

Ensure all context relevant to resolving an incident is available within the incident.

Proposal

Surface the alert details in a separate tab on the incident issue type:

Tab_2

Further details

This works 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

Release Notes

The alert payload contains critical information to solving an outage. This information needs to be easily accessible on Incidents so that you do not have to spend time searching for it potentially switching tabs or even tools in the process. In GitLab 13.4, the alert payload is available on all incidents created from alerts.

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