diff options
Diffstat (limited to 'doc/operations/incident_management/manage_incidents.md')
-rw-r--r-- | doc/operations/incident_management/manage_incidents.md | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/doc/operations/incident_management/manage_incidents.md b/doc/operations/incident_management/manage_incidents.md index 9d0c8075ff9..338dacda166 100644 --- a/doc/operations/incident_management/manage_incidents.md +++ b/doc/operations/incident_management/manage_incidents.md @@ -226,10 +226,6 @@ When you close an incident that is linked to an [alert](alerts.md), the linked alert's status changes to **Resolved**. You are then credited with the alert's status change. -<!-- Delete when the `moved_mr_sidebar` feature flag is removed --> -If you don't see this action at the top of an incident, your project or instance might have -enabled a feature flag for [moved actions](../../user/project/merge_requests/index.md#move-sidebar-actions) - ### Automatically close incidents via recovery alerts > [Introduced for HTTP integrations](https://gitlab.com/gitlab-org/gitlab/-/issues/13402) in GitLab 13.4. @@ -253,22 +249,6 @@ When GitLab receives a recovery alert, it closes the associated incident. This action is recorded as a system note on the incident indicating that it was closed automatically by the GitLab Alert bot. -## Delete an incident - -Prerequisites: - -- You must have the Owner role for a project. - -To delete an incident: - -1. In an incident, select **Incident actions** (**{ellipsis_v}**). -1. Select **Delete incident**. - -Alternatively: - -1. In an incident, select **Edit title and description** (**{pencil}**). -1. Select **Delete incident**. - ## Other actions Because incidents in GitLab are built on top of [issues](../../user/project/issues/index.md), |