Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42

12 files changed, 103 insertions, 49 deletions

diff --git a/doc/user/project/integrations/github.md b/doc/user/project/integrations/github.md
index 4f5640d9fff..019ca9da9f1 100644
--- a/doc/user/project/integrations/github.md
+++ b/doc/user/project/integrations/github.md
@@ -18,7 +18,7 @@ and is automatically configured on [GitHub import](../../../integration/github.m
 
 ## Configuration
 
-This integration requires a [GitHub API token](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token)
+This integration requires a [GitHub API token](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)
 with `repo:status` access granted.
 
 Complete these steps on GitHub:
diff --git a/doc/user/project/integrations/hangouts_chat.md b/doc/user/project/integrations/hangouts_chat.md
index 0668e5dd88f..d5dc02d5455 100644
--- a/doc/user/project/integrations/hangouts_chat.md
+++ b/doc/user/project/integrations/hangouts_chat.md
@@ -36,7 +36,7 @@ Select a room and create a webhook:
 1. Select **Save**.
 1. Copy the webhook URL.
 
-For further details, see [the Google Chat documentation for configuring webhooks](https://developers.google.com/hangouts/chat/how-tos/webhooks).
+For further details, see [the Google Chat documentation for configuring webhooks](https://developers.google.com/chat/how-tos/webhooks).
 
 ## In GitLab
 
diff --git a/doc/user/project/integrations/img/project_integrations_v13_3.png b/doc/user/project/integrations/img/project_integrations_v13_3.png
deleted file mode 100644
index 9c925d32441..00000000000
--- a/doc/user/project/integrations/img/project_integrations_v13_3.png
+++ /dev/null
diff --git a/doc/user/project/integrations/jira_cloud_configuration.md b/doc/user/project/integrations/jira_cloud_configuration.md
deleted file mode 100644
index c9ab4532760..00000000000
--- a/doc/user/project/integrations/jira_cloud_configuration.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-redirect_to: '../../../integration/jira/jira_cloud_configuration.md'
-remove_date: '2021-06-18'
----
-
-This document was moved to [another location](../../../integration/jira/jira_cloud_configuration.md).
-
-<!-- This redirect file can be deleted after <2021-06-18>. -->
-<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page -->
diff --git a/doc/user/project/integrations/jira_server_configuration.md b/doc/user/project/integrations/jira_server_configuration.md
deleted file mode 100644
index de6eec62b96..00000000000
--- a/doc/user/project/integrations/jira_server_configuration.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-redirect_to: '../../../integration/jira/jira_server_configuration.md'
-remove_date: '2021-06-18'
----
-
-This document was moved to [another location](../../../integration/jira/jira_server_configuration.md).
-
-<!-- This redirect file can be deleted after <2021-06-18>. -->
-<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page -->
diff --git a/doc/user/project/integrations/mattermost_slash_commands.md b/doc/user/project/integrations/mattermost_slash_commands.md
index 834bf15c287..619ae52481b 100644
--- a/doc/user/project/integrations/mattermost_slash_commands.md
+++ b/doc/user/project/integrations/mattermost_slash_commands.md
@@ -141,7 +141,7 @@ The available slash commands for Mattermost are:
 | ------- | ----------- | ------- |
 | <kbd>/&lt;trigger&gt; issue new &lt;title&gt; <kbd>⇧ Shift</kbd>+<kbd>↵ Enter</kbd> &lt;description&gt;</kbd> | Create a new issue in the project that `<trigger>` is tied to. `<description>` is optional. | `/gitlab issue new We need to change the homepage` |
 | <kbd>/&lt;trigger&gt; issue show &lt;issue-number&gt;</kbd> | Show the issue with ID `<issue-number>` from the project that `<trigger>` is tied to. | `/gitlab issue show 42` |
-| <kbd>/&lt;trigger&gt; deploy &lt;environment&gt; to &lt;environment&gt;</kbd> | Start the CI job that deploys from one environment to another, for example `staging` to `production`. CI/CD must be [properly configured](../../../ci/yaml/README.md). | `/gitlab deploy staging to production` |
+| <kbd>/&lt;trigger&gt; deploy &lt;environment&gt; to &lt;environment&gt;</kbd> | Start the CI job that deploys from one environment to another, for example `staging` to `production`. CI/CD must be [properly configured](../../../ci/yaml/index.md). | `/gitlab deploy staging to production` |
 
 To see a list of available commands to interact with GitLab, type the
 trigger word followed by <kbd>help</kbd>. Example: `/gitlab help`
diff --git a/doc/user/project/integrations/overview.md b/doc/user/project/integrations/overview.md
index b0ae290e7cd..53aa9da30ab 100644
--- a/doc/user/project/integrations/overview.md
+++ b/doc/user/project/integrations/overview.md
@@ -15,11 +15,9 @@ functionality to GitLab.
 You can find the available integrations under your project's
 **Settings > Integrations** page.
 
-There are more than 20 integrations to integrate with. Click on the one that you
+There are more than 20 integrations to integrate with. Select the one that you
 want to configure.
 
-![Integrations list](img/project_integrations_v13_3.png)
-
 ## Integrations listing
 
 Click on the service links to see further configuration instructions and details.
@@ -34,6 +32,7 @@ Click on the service links to see further configuration instructions and details
 | Campfire                                                  | Connect to chat.                                                                             | **{dotted-circle}** No |
 | [Confluence Workspace](../../../api/services.md#confluence-service) | Replace the link to the internal wiki with a link to a Confluence Cloud Workspace. | **{dotted-circle}** No |
 | [Custom issue tracker](custom_issue_tracker.md)           | Use a custom issue tracker.                                                                  | **{dotted-circle}** No |
+| [Datadog](../../../integration/datadog.md)                | Trace your GitLab pipelines with Datadog.                                                    | **{check-circle}** Yes |
 | [Discord Notifications](discord_notifications.md)         | Send notifications about project events to a Discord channel.                                | **{dotted-circle}** No |
 | Drone CI                                                  | Run CI/CD pipelines with Drone.                                                              | **{check-circle}** Yes |
 | [Emails on push](emails_on_push.md)                       | Send commits and diff of each push by email.                                                 | **{dotted-circle}** No |
@@ -51,7 +50,7 @@ Click on the service links to see further configuration instructions and details
 | [Microsoft Teams notifications](microsoft_teams.md)       | Receive event notifications.                                                                 | **{dotted-circle}** No |
 | Packagist                                                 | Update your projects.                                                                        | **{check-circle}** Yes |
 | Pipelines emails                                          | Send the pipeline status to a list of recipients by email.                                   | **{dotted-circle}** No |
-| PivotalTracker                                            | Use PivotalTracker as the issue tracker.                                                     | **{dotted-circle}** No |
+| [Pivotal Tracker](pivotal_tracker.md)                      | Add commit messages as comments to Pivotal Tracker stories.                                                    | **{dotted-circle}** No |
 | [Prometheus](prometheus.md)                               | Monitor application metrics.                                                                 | **{dotted-circle}** No |
 | Pushover                                                  | Get real-time notifications on your device.                                                  | **{dotted-circle}** No |
 | [Redmine](redmine.md)                                     | Use Redmine as the issue tracker.                                                            | **{dotted-circle}** No |
@@ -115,6 +114,6 @@ plugins. This allows the community to keep the plugins up to date so that they
 always work in newer GitLab versions.
 
 For an overview of what integrations are available, please see the
-[project_services source directory](https://gitlab.com/gitlab-org/gitlab/-/tree/master/app/models/project_services).
+[integrations source directory](https://gitlab.com/gitlab-org/gitlab/-/tree/master/app/models/integrations).
 
 Contributions are welcome!
diff --git a/doc/user/project/integrations/pivotal_tracker.md b/doc/user/project/integrations/pivotal_tracker.md
new file mode 100644
index 00000000000..c2c827c240b
--- /dev/null
+++ b/doc/user/project/integrations/pivotal_tracker.md
@@ -0,0 +1,47 @@
+---
+stage: Create
+group: Ecosystem
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
+---
+
+# Pivotal Tracker service **(FREE)**
+
+This service adds commit messages as comments to Pivotal Tracker stories.
+
+Once enabled, commit messages are checked for square brackets containing a hash mark followed by
+the story ID (for example, `[#555]`). Every story ID found gets the commit comment added to it.
+
+You can also close a story with a message containing: `fix [#555]`.
+You can use any of these words:
+
+- `fix`
+- `fixed`
+- `fixes`
+- `complete`
+- `completes`
+- `completed`
+- `finish`
+- `finished`
+- `finishes`
+- `delivers`
+
+Read more about the
+[Source Commits endpoint](https://www.pivotaltracker.com/help/api/rest/v5#Source_Commits) in
+the Pivotal Tracker API documentation.
+
+See also the [Pivotal Tracker service API documentation](../../../api/services.md#pivotal-tracker).
+
+## Set up Pivotal Tracker
+
+In Pivotal Tracker, [create an API token](https://www.pivotaltracker.com/help/articles/api_token/).
+
+Complete these steps in GitLab:
+
+1. Go to the project you want to configure.
+1. Go to the [Integrations page](overview.md#accessing-integrations).
+1. Select **Pivotal Tracker**.
+1. Ensure that the **Active** toggle is enabled.
+1. Paste the token you generated in Pivotal Tracker.
+1. (Optional) To restrict this setting to specific branches, list them in the **Restrict to branch**
+   field, separated with commas.
+1. Select **Save changes** or optionally select **Test settings**.
diff --git a/doc/user/project/integrations/prometheus_library/index.md b/doc/user/project/integrations/prometheus_library/index.md
index 584c0898fec..fe74ea6834b 100644
--- a/doc/user/project/integrations/prometheus_library/index.md
+++ b/doc/user/project/integrations/prometheus_library/index.md
@@ -35,6 +35,6 @@ In order to isolate and only display relevant metrics for a given environment,
 GitLab needs a method to detect which labels are associated. To do that,
 GitLab uses the defined queries and fills in the environment specific variables.
 Typically this involves looking for the
-[`$CI_ENVIRONMENT_SLUG`](../../../../ci/variables/README.md#predefined-cicd-variables),
+[`$CI_ENVIRONMENT_SLUG`](../../../../ci/variables/index.md#predefined-cicd-variables),
 but may also include other information such as the project's Kubernetes namespace.
 Each search query is defined in the [exporter specific documentation](#exporters).
diff --git a/doc/user/project/integrations/prometheus_library/kubernetes.md b/doc/user/project/integrations/prometheus_library/kubernetes.md
index 1bafa4938af..ea0119f2e94 100644
--- a/doc/user/project/integrations/prometheus_library/kubernetes.md
+++ b/doc/user/project/integrations/prometheus_library/kubernetes.md
@@ -40,7 +40,7 @@ Prometheus needs to be deployed into the cluster and configured properly in orde
 
 In order to isolate and only display relevant CPU and Memory metrics for a given environment, GitLab needs a method to detect which containers it is running. Because these metrics are tracked at the container level, traditional Kubernetes labels are not available.
 
-Instead, the [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) or [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) name should begin with [CI_ENVIRONMENT_SLUG](../../../../ci/variables/README.md#predefined-cicd-variables). It can be followed by a `-` and additional content if desired. For example, a deployment name of `review-homepage-5620p5` would match the `review/homepage` environment.
+Instead, the [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) or [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) name should begin with [CI_ENVIRONMENT_SLUG](../../../../ci/variables/index.md#predefined-cicd-variables). It can be followed by a `-` and additional content if desired. For example, a deployment name of `review-homepage-5620p5` would match the `review/homepage` environment.
 
 ## Displaying Canary metrics **(PREMIUM)**
 
diff --git a/doc/user/project/integrations/webex_teams.md b/doc/user/project/integrations/webex_teams.md
index 05515c58161..2851fe0b299 100644
--- a/doc/user/project/integrations/webex_teams.md
+++ b/doc/user/project/integrations/webex_teams.md
@@ -13,7 +13,7 @@ You can configure GitLab to send notifications to a Webex Teams space:
 
 ## Create a webhook for the space
 
-1. Go to the [Incoming Webhooks app page](https://apphub.webex.com/messaging/applications/incoming-webhooks-cisco-systems-38054).
+1. Go to the [Incoming Webhooks app page](https://apphub.webex.com/applications/incoming-webhooks-cisco-systems-38054).
 1. Select **Connect** and log in to Webex Teams, if required.
 1. Enter a name for the webhook and select the space to receive the notifications.
 1. Select **ADD**.
diff --git a/doc/user/project/integrations/webhooks.md b/doc/user/project/integrations/webhooks.md
index 406b1e9ba6b..01f3424d993 100644
--- a/doc/user/project/integrations/webhooks.md
+++ b/doc/user/project/integrations/webhooks.md
@@ -112,7 +112,7 @@ branches, this hook isn't executed.
 X-Gitlab-Event: Push Hook
 ```
 
-**Request body:**
+**Payload example:**
 
 ```json
 {
@@ -202,7 +202,7 @@ tags, this hook is not executed.
 X-Gitlab-Event: Tag Push Hook
 ```
 
-**Request body:**
+**Payload example:**
 
 ```json
 {
@@ -256,7 +256,14 @@ Triggered when a new issue is created or an existing issue was updated/closed/re
 X-Gitlab-Event: Issue Hook
 ```
 
-**Request body:**
+**Available `object_attributes.action`:**
+
+- `open`
+- `close`
+- `reopen`
+- `update`
+
+**Payload example:**
 
 ```json
 {
@@ -423,7 +430,7 @@ Valid target types:
 X-Gitlab-Event: Note Hook
 ```
 
-**Request body:**
+**Payload example:**
 
 ```json
 {
@@ -505,7 +512,7 @@ X-Gitlab-Event: Note Hook
 X-Gitlab-Event: Note Hook
 ```
 
-**Request body:**
+**Payload example:**
 
 ```json
 {
@@ -634,7 +641,7 @@ X-Gitlab-Event: Note Hook
 X-Gitlab-Event: Note Hook
 ```
 
-**Request body:**
+**Payload example:**
 
 ```json
 {
@@ -742,7 +749,7 @@ NOTE:
 X-Gitlab-Event: Note Hook
 ```
 
-**Request body:**
+**Payload example:**
 
 ```json
 {
@@ -820,7 +827,17 @@ Triggered when a new merge request is created, an existing merge request was upd
 X-Gitlab-Event: Merge Request Hook
 ```
 
-**Request body:**
+**Available `object_attributes.action`:**
+
+- `open`
+- `close`
+- `reopen`
+- `update`
+- `approved`
+- `unapproved`
+- `merge`
+
+**Payload example:**
 
 ```json
 {
@@ -983,7 +1000,7 @@ Triggered when a wiki page is created, updated or deleted.
 X-Gitlab-Event: Wiki Page Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1044,7 +1061,7 @@ Triggered on status change of Pipeline.
 X-Gitlab-Event: Pipeline Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1291,7 +1308,7 @@ Triggered on status change of a job.
 X-Gitlab-Event: Job Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1340,7 +1357,7 @@ X-Gitlab-Event: Job Hook
   },
   "runner": {
     "active": true,
-    "runner_type": "project_type", 
+    "runner_type": "project_type",
     "is_shared": false,
     "id": 380987,
     "description": "shared-runners-manager-6.gitlab.com",
@@ -1370,7 +1387,7 @@ Triggered when a deployment:
 X-Gitlab-Event: Deployment Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1433,7 +1450,7 @@ Member events are triggered when:
 X-Gitlab-Event: Member Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1461,7 +1478,7 @@ X-Gitlab-Event: Member Hook
 X-Gitlab-Event: Member Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1489,7 +1506,7 @@ X-Gitlab-Event: Member Hook
 X-Gitlab-Event: Member Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1526,7 +1543,7 @@ Subgroup events are triggered when:
 X-Gitlab-Event: Subgroup Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1554,7 +1571,7 @@ X-Gitlab-Event: Subgroup Hook
 X-Gitlab-Event: Subgroup Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1587,7 +1604,7 @@ Triggered when a feature flag is turned on or off.
 X-Gitlab-Event: Feature Flag Hook
 ```
 
-**Request Body**:
+**Payload example**:
 
 ```json
 {
@@ -1637,7 +1654,12 @@ Triggered when a release is created or updated.
 X-Gitlab-Event: Release Hook
 ```
 
-**Request Body**:
+**Available `object_attributes.action`:**
+
+- `create`
+- `update`
+
+**Payload example**:
 
 ```json
 {
@@ -1762,6 +1784,10 @@ On this page, you can see data that GitLab sends (request headers and body) and
 From this page, you can repeat delivery with the same data by clicking `Resend Request` button.
 
 NOTE:
+This history is unavailable for Group-level webhooks. For more information, read
+[issue #325642](https://gitlab.com/gitlab-org/gitlab/-/issues/325642).
+
+NOTE:
 If URL or secret token of the webhook were updated, data is delivered to the new address.
 
 ### Webhook fails or multiple webhook requests are triggered