Revert "Always sync alert escalation attributes to incidents"
What does this MR do and why?
Reverts !84139 (merged) in line with !83159 (comment 904704277).
Related issue: #356215 (closed)
Screenshots or screen recordings
There are no UI changes. Screenshots represent verification flow.
Creating new alert | Creating new incident w/o flag enabled | Incident after enabling the flag |
---|---|---|
How to set up and validate locally
- Disable the feature flag if enabled
Feature.disable(:incident_escalations)
- Create an incident from an alert in the UI
-
https://docs.gitlab.com/ee/operations/incident_management/integrations.html#triggering-test-alerts (
project > Settings > Monitor > Alerts
, pick a name, set to active, skip to "Save")- Sample payload
{ "title": "Creating an incident from an alert" }
- Sample payload
- Open alert list under
project > Monitor > Alerts
& click the recent row to open alert details - Click 'Create Incident` (or open the associated incident if it was auto-created)
-
https://docs.gitlab.com/ee/operations/incident_management/integrations.html#triggering-test-alerts (
- Check that an
IncidentManagement::IssuableEscalationStatus
record wasn't created by enabling the feature flag & refreshing the page/restart gdk (you should seeNone
for the Status/Escalation policy fields)Feature.enable(:incident_escalations)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Sarah Yasonik