Introduce related alerts to incidents
Proposal
- Change some of the verbiage around Linked Issues for the Incident Issue type (all changes are also captured in the designs below as well!):
- Existing
Linked issues
text becomesLinked incidents, issues & alerts
- When a user clicks on the
+
sign and expands the form,The current issue
text changes toThe current incident
. - In the same expanded form,
the following issue(s)
becomesthe following incident(s) or issue(s)
. - An additional field is added for inputing alerts. This field is displayed by default, and can be hidden if
blocks
oris blocked by
is selected in the form radio buttons.
- Allow for Alerts to be linked in addition to related Incidents and Issues to the Incident Issue type.
Designs
Default state | Adding related content |
---|---|
Note: the related issue and related merge request widgets are currently being unboxed in !87886 (closed). We should plan on matching the styling of this new links widget to whatever work is done in that MR. Here's how that might look, depending on how the design is finalized in that MR.
Intended users
Metrics
Increase Monitor - SMAU, Unique users that interact with Alerts and Incidents AND Monitor - AMAU - Alerts Active Users
Implementation
-
Stop syncing alert & incident statuses entirely (or showing an alert's escalation policy on the incident page). -
Allow incident escalations on any incident, regardless of alerts. -
Swap issues to allow many associated alerts. ( has_one
->has_many
)
Edited by Sarah Yasonik