Design: Vision mock-up for promoting alerts to incidents
Problem to solve
We are investigating the idea of making incidents a separate entity within GitLab. If we do this, we'll need to re-imagine the workflow for how an alert becomes an incident.
Intended users
User experience goal
Proposal
Default list and incident view | Hover ACK | Hover Snooze | Hover Undo ACK (would change it back to triggered) | Full alert details | Alert timeline | Promoted incident | Incident timeline |
---|---|---|---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Further details
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
Edited by Amelia Bauerly