From 7a152b4612bd872cdf8de41bf848ab65b55ece7f Mon Sep 17 00:00:00 2001
From: Filip Aleksic <faleksic@gitlab.com>
Date: Fri, 19 Apr 2024 12:44:42 +0000
Subject: [PATCH] Remove outdated references from Respond docs
---
doc/administration/logs/index.md | 36 ++-----------------
.../performance/gitlab_configuration.md | 15 +-------
.../performance/grafana_configuration.md | 4 ---
.../incident_management_rate_limits.md | 2 --
doc/api/metrics_dashboard_annotations.md | 2 --
doc/api/metrics_user_starred_dashboards.md | 4 ---
doc/operations/incident_management/alerts.md | 15 +-------
.../escalation_policies.md | 2 --
.../incident_management/incidents.md | 10 ------
doc/operations/incident_management/index.md | 2 --
.../incident_management/integrations.md | 26 ++------------
.../incident_management/manage_incidents.md | 13 -------
.../incident_management/oncall_schedules.md | 2 --
doc/operations/incident_management/paging.md | 2 --
.../incident_management/status_page.md | 6 +---
doc/user/project/service_desk/configure.md | 5 ---
.../service_desk/using_service_desk.md | 2 --
17 files changed, 7 insertions(+), 141 deletions(-)
diff --git a/doc/administration/logs/index.md b/doc/administration/logs/index.md
index 9f72b45737a7..7f7de6182a77 100644
--- a/doc/administration/logs/index.md
+++ b/doc/administration/logs/index.md
@@ -219,7 +219,7 @@ The ActionCable connection or channel class is used as the `controller`.
```
NOTE:
-Starting with GitLab 12.5, if an error occurs, an
+If an error occurs, an
`exception` field is included with `class`, `message`, and
`backtrace`. Previous versions included an `error` field instead of
`exception.class` and `exception.message`. For example:
@@ -377,8 +377,6 @@ October 07, 2014 11:25: Project "project133" was removed
## `application_json.log`
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/22812) in GitLab 12.7.
-
This file is located at:
- `/var/log/gitlab/gitlab-rails/application_json.log` on Linux package installations.
@@ -453,9 +451,6 @@ This file is located at:
- `/var/log/gitlab/gitlab-rails/git_json.log` on Linux package installations.
- `/home/git/gitlab/log/git_json.log` on self-compiled installations.
-After GitLab version 12.2, this file was renamed from `githost.log` to
-`git_json.log` and stored in JSON format.
-
GitLab has to interact with Git repositories, but in some rare cases
something can go wrong. If this happens, you need to know exactly what
happened. This log file contains all failed requests from GitLab to Git
@@ -581,8 +576,6 @@ For self-compiled installations, edit the `gitlab.yml` and set the Sidekiq
### `sidekiq_client.log`
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26586) in GitLab 12.9.
-
This file is located at:
- `/var/log/gitlab/gitlab-rails/sidekiq_client.log` on Linux package installations.
@@ -709,8 +702,6 @@ This file logs the progress of [project imports and migrations](../../user/proje
## `exporter.log`
-> - Introduced in GitLab 13.1.
-
This file is located at:
- `/var/log/gitlab/gitlab-rails/exporter.log` on Linux package installations.
@@ -720,8 +711,6 @@ It logs the progress of the export process.
## `features_json.log`
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/59587) in GitLab 13.7.
-
This file is located at:
- `/var/log/gitlab/gitlab-rails/features_json.log` on Linux package installations.
@@ -763,8 +752,6 @@ The examples show the `resource_group_id`, `processable_id`, `message`, and `suc
## `auth.log`
-> - Introduced in GitLab 12.0.
-
This file is located at:
- `/var/log/gitlab/gitlab-rails/auth.log` on Linux package installations.
@@ -774,8 +761,7 @@ This log records:
- Requests over the [Rate Limit](../settings/rate_limits_on_raw_endpoints.md) on raw endpoints.
- [Protected paths](../settings/protected_paths.md) abusive requests.
-- In GitLab versions [12.3](https://gitlab.com/gitlab-org/gitlab/-/issues/29239) and later,
- user ID and username, if available.
+- User ID and username, if available.
## `auth_json.log`
@@ -801,8 +787,6 @@ This file contains the JSON version of the logs in `auth.log`, for example:
## `graphql_json.log`
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/59587) in GitLab 12.0.
-
This file is located at:
- `/var/log/gitlab/gitlab-rails/graphql_json.log` on Linux package installations.
@@ -823,8 +807,6 @@ The `clickhouse.log` file logs information related to the
## `migrations.log`
-> - Introduced in GitLab 12.3.
-
This file is located at:
- `/var/log/gitlab/gitlab-rails/migrations.log` on Linux package installations.
@@ -834,8 +816,6 @@ This file logs the progress of [database migrations](../raketasks/maintenance.md
## `mail_room_json.log` (default)
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/19186) in GitLab 12.6.
-
This file is located at:
- `/var/log/gitlab/mailroom/current` on Linux package installations.
@@ -898,8 +878,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** Self-managed
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/15442) in GitLab 12.3.
-
Contains details of GitLab [Database Load Balancing](../postgresql/database_load_balancing.md).
This file is located at:
@@ -926,8 +904,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** Self-managed
-> - Introduced in GitLab 12.6.
-
This file logs information related to the Elasticsearch Integration, including
errors during indexing or searching Elasticsearch. This file is located at:
@@ -953,8 +929,6 @@ Line breaks have been added to the following example line for clarity:
## `exceptions_json.log`
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/17819) in GitLab 12.6.
-
This file logs the information about exceptions being tracked by
`Gitlab::ErrorTracking`, which provides a standard and consistent way of
[processing rescued exceptions](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/logging.md#exception-handling).
@@ -984,8 +958,6 @@ Each line contains JSON that can be ingested by Elasticsearch. For example:
## `service_measurement.log`
-> - Introduced in GitLab 13.0.
-
This file is located at:
- `/var/log/gitlab/gitlab-rails/service_measurement.log` on Linux package installations.
@@ -1210,16 +1182,12 @@ GitLab also tracks [Prometheus metrics for Praefect](../gitaly/monitoring.md#mon
## Backup log
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63832) in GitLab 14.1.
-
For Linux package installations, the backup log is located at `/var/log/gitlab/gitlab-rails/backup_json.log`.
This log is populated when a [GitLab backup is created](../../administration/backup_restore/index.md). You can use this log to understand how the backup process performed.
## Performance bar stats
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/48149) in GitLab 13.7.
-
This file is located at:
- `/var/log/gitlab/gitlab-rails/performance_bar_json.log` on Linux package installations.
diff --git a/doc/administration/monitoring/performance/gitlab_configuration.md b/doc/administration/monitoring/performance/gitlab_configuration.md
index 458d586c8035..d02272873ca8 100644
--- a/doc/administration/monitoring/performance/gitlab_configuration.md
+++ b/doc/administration/monitoring/performance/gitlab_configuration.md
@@ -10,20 +10,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed
-GitLab Performance Monitoring is disabled by default. To enable it and change any of its
-settings:
-
-1. On the left sidebar, at the bottom, select **Admin Area**.
-1. Select **Settings > Metrics and profiling**.
-1. Add the necessary configuration changes.
-1. Restart all GitLab for the changes to take effect:
-
- - For Linux package installations: `sudo gitlab-ctl restart`
- - For self-compiled installations: `sudo service gitlab restart`
-
-NOTE:
-Removed [in GitLab 13.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/30786). Use the
-[Prometheus integration](../prometheus/index.md) instead.
+See [Prometheus integration](../prometheus/index.md).
## Pending migrations
diff --git a/doc/administration/monitoring/performance/grafana_configuration.md b/doc/administration/monitoring/performance/grafana_configuration.md
index e353e03f5570..d517a4b9fa6d 100644
--- a/doc/administration/monitoring/performance/grafana_configuration.md
+++ b/doc/administration/monitoring/performance/grafana_configuration.md
@@ -30,8 +30,6 @@ see the [GitLab Grafana dashboards](https://gitlab.com/gitlab-org/grafana-dashbo
## Integrate with GitLab UI
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/61005) in GitLab 12.1.
-
After setting up Grafana, you can enable a link to access it from the
GitLab sidebar:
@@ -46,8 +44,6 @@ GitLab displays your link in the Admin Area under **Monitoring > Metrics Dashboa
## Required Scopes
-> - [Introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5822) in GitLab 13.10.
-
When setting up Grafana through the process above, no scope shows in the screen in
the Admin Area under **Applications > GitLab Grafana**. However, the `read_user` scope is
required and is provided to the application automatically. Setting any scope other than
diff --git a/doc/administration/settings/incident_management_rate_limits.md b/doc/administration/settings/incident_management_rate_limits.md
index 629fbc13f1fd..6778da18cf53 100644
--- a/doc/administration/settings/incident_management_rate_limits.md
+++ b/doc/administration/settings/incident_management_rate_limits.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Ultimate
**Offering:** Self-managed
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/17859) in GitLab 12.5.
-
You can limit the number of inbound alerts for [incidents](../../operations/incident_management/incidents.md)
that can be created in a period of time. The inbound [incident management](../../operations/incident_management/index.md)
alert limit can help prevent overloading your incident responders by reducing the
diff --git a/doc/api/metrics_dashboard_annotations.md b/doc/api/metrics_dashboard_annotations.md
index a3e1efe75eec..68f00e837687 100644
--- a/doc/api/metrics_dashboard_annotations.md
+++ b/doc/api/metrics_dashboard_annotations.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29089) in GitLab 12.10 behind a disabled feature flag.
-
Metrics dashboard annotations allow you to indicate events on your graphs at a single point in time or over a time span.
## Create a new annotation
diff --git a/doc/api/metrics_user_starred_dashboards.md b/doc/api/metrics_user_starred_dashboards.md
index 06275119ff93..7d90840b1898 100644
--- a/doc/api/metrics_user_starred_dashboards.md
+++ b/doc/api/metrics_user_starred_dashboards.md
@@ -15,8 +15,6 @@ by displaying favorited dashboards at the top of the select list.
## Add a star to a dashboard
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/31316) in GitLab 13.0.
-
```plaintext
POST /projects/:id/metrics/user_starred_dashboards
```
@@ -46,8 +44,6 @@ Example Response:
## Remove a star from a dashboard
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/31892) in GitLab 13.0.
-
```plaintext
DELETE /projects/:id/metrics/user_starred_dashboards
```
diff --git a/doc/operations/incident_management/alerts.md b/doc/operations/incident_management/alerts.md
index 446364b466e1..cea7fe464e7b 100644
--- a/doc/operations/incident_management/alerts.md
+++ b/doc/operations/incident_management/alerts.md
@@ -22,7 +22,6 @@ The alert list displays the following information:
- **Search**: The alert list supports a simple free text search on the title,
description, monitoring tool, and service fields.
- ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/213884) in GitLab 13.1.)
- **Severity**: The current importance of a alert and how much attention it
should receive. For a listing of all statuses, read [Alert Management severity](#alert-severity).
- **Start time**: How long ago the alert fired. This field uses the standard
@@ -71,10 +70,7 @@ The **Alert details** tab has two sections. The top section provides a short lis
### Metrics tab
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/217768) in GitLab 13.2.
-> - [Changed](https://gitlab.com/gitlab-org/gitlab/-/issues/340852) in GitLab 14.10. In GitLab 14.9 and earlier, this tab shows a metrics chart for alerts coming from Prometheus.
-
-In many cases, alerts are associated to metrics. You can upload screenshots of metric charts in the **Metrics** tab.
+This tab shows a metrics chart for alerts coming from Prometheus. In many cases, alerts are associated to metrics. You can upload screenshots of metric charts in the **Metrics** tab.
To do so, either:
@@ -89,8 +85,6 @@ If you add a link, it is shown above the uploaded image.
### Activity feed tab
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3066) in GitLab 13.1.
-
The **Activity feed** tab is a log of activity on the alert. When you take action on an alert, this is logged as a system note. This gives you a linear timeline of the alert's investigation and assignment history.
The following actions result in a system note:
@@ -160,8 +154,6 @@ In GitLab 15.1 and earlier, updating the status of an [alert with an associated
### Assign an alert
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3066) in GitLab 13.1.
-
In large teams, where there is shared ownership of an alert, it can be difficult to track who is investigating and working on it. Assigning alerts eases collaboration and delegation by indicating which user is owning the alert. GitLab supports only a single assignee per alert.
To assign an alert:
@@ -186,8 +178,6 @@ After completing their portion of investigating or fixing the alert, users can u
### Create a to-do item from an alert
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3066) in GitLab 13.1.
-
You can manually create a [to-do item](../../user/todos.md) for yourself from an alert, and view it later on your **To-Do List**.
To add a to-do item, on the right sidebar, select **Add a to do**.
@@ -198,9 +188,6 @@ DETAILS:
**Tier:** Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - Introduced in GitLab 13.1: incidents are not created automatically by default.
-> - Mapping common severity values from the alert payload [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50871) in GitLab 13.9.
-
Turn on creating [incidents](incidents.md) automatically whenever an alert is triggered.
Prerequisites:
diff --git a/doc/operations/incident_management/escalation_policies.md b/doc/operations/incident_management/escalation_policies.md
index 8ba47aea867f..6e00497631f4 100644
--- a/doc/operations/incident_management/escalation_policies.md
+++ b/doc/operations/incident_management/escalation_policies.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4638) in GitLab 14.1.
-
Escalation Policies protect your company from missed critical alerts. Escalation Policies contain
time-boxed steps that automatically page the next responder in the escalation step if the responder
in the previous step has not responded. You can create an escalation policy in the GitLab project
diff --git a/doc/operations/incident_management/incidents.md b/doc/operations/incident_management/incidents.md
index dc9905254fab..3740fd6bc592 100644
--- a/doc/operations/incident_management/incidents.md
+++ b/doc/operations/incident_management/incidents.md
@@ -52,8 +52,6 @@ For an example of the incident list in action, see this
### Sort the incident list
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229534) in GitLab 13.3: incidents are sorted by created date by default.
-
The incident list shows incidents sorted by incident created date, showing the newest first.
To sort by another column, or to change the sorting order, select the column.
@@ -107,8 +105,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/235994) in GitLab 13.8.
-
In many cases, incidents are associated to metrics. You can upload screenshots of metric
charts in the **Metrics** tab:
@@ -122,8 +118,6 @@ If you add a link, you can access the original graph by selecting the hyperlink
### Alert details
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/230847) in GitLab 13.4.
-
Incidents show the details of linked alerts in a separate tab. To populate this
tab, the incident must have been created with a linked alert. Incidents
created automatically from alerts have this
@@ -144,8 +138,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/227836) in GitLab 13.5.
-
To see the latest updates on an incident, select
**Turn recent updates view on** (**{history}**) on the comment bar. Comments display
un-threaded and chronologically, newest to oldest.
@@ -156,8 +148,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241663) in GitLab 13.5.
-
You can enable the Service Level Agreement Countdown timer on incidents to track
the Service Level Agreements (SLA) you hold with your customers. The timer is
automatically started when the incident is created, and shows the time
diff --git a/doc/operations/incident_management/index.md b/doc/operations/incident_management/index.md
index fbf99a48bb8c..aa1b6dd1815b 100644
--- a/doc/operations/incident_management/index.md
+++ b/doc/operations/incident_management/index.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2877) in GitLab 13.0.
-
Incident Management enables developers to easily triage and view the alerts and incidents
generated by their application. By surfacing alerts and incidents where the code is
being developed, efficiency and awareness can be increased. Check out the following sections for more information:
diff --git a/doc/operations/incident_management/integrations.md b/doc/operations/incident_management/integrations.md
index 5bd58b7dbb60..a0fc38ab50bf 100644
--- a/doc/operations/incident_management/integrations.md
+++ b/doc/operations/incident_management/integrations.md
@@ -10,16 +10,11 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13203) in GitLab 12.4.
-> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/42640) from GitLab Ultimate to GitLab Free in 12.8.
-
GitLab can accept alerts from any source via a webhook receiver. [Alert notifications](alerts.md)
can [trigger paging](paging.md#paging) for on-call rotations or be used to [create incidents](manage_incidents.md#from-an-alert).
## Integrations list
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/245331) in GitLab 13.5.
-
With at least the Maintainer role, you can view the list of configured
alerts integrations by navigating to **Settings > Monitor**
in your project's sidebar menu, and expanding the **Alerts** section. The list displays
@@ -52,8 +47,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4442) in GitLab 13.6.
-
In [GitLab Premium](https://about.gitlab.com/pricing/), you can create multiple
unique HTTP endpoints to receive alerts from any external source in JSON format,
and you can [customize the payload](#customize-the-alert-payload-outside-of-gitlab).
@@ -85,8 +78,6 @@ side of the integrations list.
#### Map fields in custom alerts
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4443) in GitLab 13.10.
-
You can integrate your monitoring tool's alert format with GitLab alerts. To show the
correct information in the [Alert list](alerts.md) and the
[Alert Details page](alerts.md#alert-details-page), map your alert's fields to
@@ -244,8 +235,6 @@ Ensure your requests are smaller than the
#### Prometheus severity options
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50871) in GitLab 13.9
-
Alerts from Prometheus can provide any of the case-insensitive follow values for [alert severity](../incident_management/alerts.md#alert-severity):
- **Critical**: `critical`, `s1`, `p1`, `emergency`, `fatal`
@@ -366,8 +355,6 @@ using one of the above header options if your tooling supports it.
## Response body
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/342730) in GitLab 14.5.
-
The JSON response body contains a list of any alerts created within the request:
```json
@@ -387,8 +374,6 @@ Successful responses return a `200` response code.
## Triggering test alerts
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3066) in GitLab in 13.2.
-
After a [project maintainer or owner](../../user/permissions.md)
configures an integration, you can trigger a test
alert to confirm your integration works properly.
@@ -409,10 +394,7 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214557) in GitLab 13.2.
-
-In GitLab versions 13.2 and greater, GitLab groups alerts based on their
-payload. When an incoming alert contains the same payload as another alert
+GitLab groups alerts based on their payload. When an incoming alert contains the same payload as another alert
(excluding the `start_time` and `hosts` attributes), GitLab groups these alerts
together and displays a counter on the [Alert Management List](incidents.md)
and details pages.
@@ -423,8 +405,6 @@ If the existing alert is already `resolved`, GitLab creates a new alert instead.
## Recovery alerts
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13402) in GitLab 13.4.
-
The alert in GitLab is automatically resolved when an HTTP Endpoint
receives a payload with the end time of the alert set. For HTTP Endpoints
without [custom mappings](#map-fields-in-custom-alerts), the expected
@@ -448,9 +428,7 @@ DETAILS:
WARNING:
We are building deeper integration with Opsgenie and other alerting tools through
[HTTP endpoint integrations](#single-http-endpoint) so you can see alerts in
-the GitLab interface. As a result, the previous direct link to Opsgenie Alerts from
-the GitLab alerts list is deprecated in
-GitLab versions [13.8 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/273657).
+the GitLab interface.
You can monitor alerts using a GitLab integration with [Opsgenie](https://www.atlassian.com/software/opsgenie).
diff --git a/doc/operations/incident_management/manage_incidents.md b/doc/operations/incident_management/manage_incidents.md
index 3e3754f91800..40234efbaa9e 100644
--- a/doc/operations/incident_management/manage_incidents.md
+++ b/doc/operations/incident_management/manage_incidents.md
@@ -18,10 +18,6 @@ You can create an incident manually or automatically.
### From the incidents list
-> - [Moved](https://gitlab.com/gitlab-org/monitor/monitor/-/issues/24) to GitLab Free in 13.3.
-> - [Permission changed](https://gitlab.com/gitlab-org/gitlab/-/issues/336624) from Guest to Reporter in GitLab 14.5.
-> - Automatic application of the `incident` label [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/290964) in GitLab 14.8.
-
Prerequisites:
- You must have at least the Reporter role for the project.
@@ -34,8 +30,6 @@ To create an incident from the incidents list:
### From the issues list
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/230857) in GitLab 13.4.
-
Prerequisites:
- You must have at least the Reporter role for the project.
@@ -50,8 +44,6 @@ To create an incident from the issues list:
### From an alert
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/217745) in GitLab 13.1.
-
Create an incident issue when viewing an [alert](alerts.md).
The incident description is populated from the alert.
@@ -83,7 +75,6 @@ whenever an alert is triggered.
### Using the PagerDuty webhook
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/119018) in GitLab 13.3.
> - [PagerDuty V3 Webhook](https://support.pagerduty.com/docs/webhooks) support [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/383029) in GitLab 15.7.
You can set up a webhook with PagerDuty to automatically create a GitLab incident
@@ -142,8 +133,6 @@ To assign a user:
## Change severity
-> - Editing severity on incident details page was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229402) in GitLab 13.4.
-
See [incident list](incidents.md#incidents-list) for a full description of the severity levels available.
Prerequisites:
@@ -231,8 +220,6 @@ You are then credited with the alert's status change.
### Automatically close incidents via recovery alerts
-> - [Introduced for HTTP integrations](https://gitlab.com/gitlab-org/gitlab/-/issues/13402) in GitLab 13.4.
-
Turn on closing an incident automatically when GitLab receives a recovery alert
from a HTTP or Prometheus webhook.
diff --git a/doc/operations/incident_management/oncall_schedules.md b/doc/operations/incident_management/oncall_schedules.md
index 24eaa4b5368a..0f3fc220a492 100644
--- a/doc/operations/incident_management/oncall_schedules.md
+++ b/doc/operations/incident_management/oncall_schedules.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4544) in GitLab 13.11.
-
Use on-call schedule management to create schedules for responders to rotate on-call
responsibilities. Maintain the availability of your software services by putting your teams on-call.
With [escalation policies](escalation_policies.md) and on-call schedules, your team is notified immediately
diff --git a/doc/operations/incident_management/paging.md b/doc/operations/incident_management/paging.md
index 5cd7b458deab..9c3f0fb0728b 100644
--- a/doc/operations/incident_management/paging.md
+++ b/doc/operations/incident_management/paging.md
@@ -16,8 +16,6 @@ notifications using the methods described on this page.
## Slack notifications
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216326) in GitLab 13.1.
-
The GitLab for Slack app can be used to receive important incident notifications.
When [the GitLab for Slack app is configured](slack.md), incident responders are notified in Slack
diff --git a/doc/operations/incident_management/status_page.md b/doc/operations/incident_management/status_page.md
index b745355b6ad0..274908c8d4b7 100644
--- a/doc/operations/incident_management/status_page.md
+++ b/doc/operations/incident_management/status_page.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2479) in GitLab 12.10.
-
With a GitLab Status Page, you can create and deploy a static website to communicate
efficiently to users during an incident. The Status Page landing page displays an
overview of recent incidents:
@@ -26,7 +24,7 @@ Selecting an incident displays a detail page with more information about a parti
- The incident title, including any emoji.
- The description of the incident, including emoji.
- Any file attachments provided in the incident description, or comments with a
- valid image extension. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/205166) in GitLab 13.1.
+ valid image extension.
- A chronological ordered list of updates to the incident.
## Set up a Status Page
@@ -142,7 +140,6 @@ you provided during setup. As part of publication, GitLab:
- Anonymizes user and group mentions with `Incident Responder`.
- Removes titles of non-public [GitLab references](../../user/markdown.md#gitlab-specific-references).
- Publishes any files attached to incident issue descriptions, up to 5000 per issue.
- ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/205166) in GitLab 13.1.)
After publication, you can access the incident's details page by selecting the
**Published on status page** button displayed under the Incident's title.
@@ -166,7 +163,6 @@ To publish comments to the Status Page Incident:
adding a microphone [emoji reaction](../../user/emoji_reactions.md)
reaction (`:microphone:` 🎤) to the comment.
- Any files attached to the comment (up to 5000 per issue) are also published.
- ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/205166) in GitLab 13.1.)
WARNING:
Anyone with access to view the Issue can add an emoji reaction to a comment, so
diff --git a/doc/user/project/service_desk/configure.md b/doc/user/project/service_desk/configure.md
index 3fbf1159ce63..f0bb48a500ec 100644
--- a/doc/user/project/service_desk/configure.md
+++ b/doc/user/project/service_desk/configure.md
@@ -50,7 +50,6 @@ To improve your Service Desk project's security, you should:
## Customize emails sent to the requester
-> - Moved from GitLab Premium to GitLab Free in 13.2.
> - `UNSUBSCRIBE_URL`, `SYSTEM_HEADER`, `SYSTEM_FOOTER`, and `ADDITIONAL_TEXT` placeholders [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/285512) in GitLab 15.9.
> - `%{ISSUE_DESCRIPTION}` [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/223751) in GitLab 16.0.
> - `%{ISSUE_URL}` [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/408793) in GitLab 16.1.
@@ -460,9 +459,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/2201) in GitLab 13.0.
-> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/284656) in GitLab 13.8.
-
You can use an additional alias email address for Service Desk on an instance level.
To do this, you must configure
@@ -670,7 +666,6 @@ read about [Helm IMAP secrets](https://docs.gitlab.com/charts/installation/secre
#### Microsoft Graph
-> - Alternative Azure deployments [introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/5978) in GitLab 14.9.
> - [Introduced for self-compiled (source) installs](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/116494) in GitLab 15.11.
`service_desk_email` can be configured to read Microsoft Exchange Online mailboxes with the Microsoft
diff --git a/doc/user/project/service_desk/using_service_desk.md b/doc/user/project/service_desk/using_service_desk.md
index 0c17336b8ba0..054918343ccd 100644
--- a/doc/user/project/service_desk/using_service_desk.md
+++ b/doc/user/project/service_desk/using_service_desk.md
@@ -24,8 +24,6 @@ The email address is available at the top of the issue list.
## As an end user (issue creator)
-> - Support for additional email headers [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/346600) in GitLab 14.6. In earlier versions, the Service Desk email address had to be in the "To" field.
-
To create a Service Desk issue, an end user does not need to know anything about
the GitLab instance. They just send an email to the address they are given, and
receive an email back confirming receipt:
--
GitLab