Add latest changes from gitlab-org/gitlab@master

11 files changed, 248 insertions, 61 deletions

diff --git a/doc/administration/whats-new.md b/doc/administration/whats-new.md
new file mode 100644
index 00000000000..4cbb0b854ae
--- /dev/null
+++ b/doc/administration/whats-new.md
@@ -0,0 +1,29 @@
+---
+stage: Growth
+group: Adoption
+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
+---
+
+# What's new **(FREE)**
+
+With each monthly release, GitLab includes some of the highlights from the last 10
+GitLab versions in the **What's new** feature. To access it:
+
+1. In the top navigation bar, select the **{question}** icon.
+1. Select **What's new** from the menu.
+
+The **What's new** describes new features available in multiple
+[GitLab tiers](https://about.gitlab.com/pricing). While all users can see the
+feature list, the feature list is tailored to your subscription type:
+
+- Features only available to self-managed installations are not shown on GitLab.com.
+- Features only available on GitLab.com are not shown to self-managed installations.
+
+The **What's new** feature cannot be disabled, but
+[is planned](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/59011) for a future release.
+
+## Self-managed installations
+
+Due to our release post process, the content for **What's new** is not yet finalized
+when a new version (`.0` release) is cut. The updated **What's new** is included
+in the first patch release, such as `13.10.1`.
diff --git a/doc/api/api_resources.md b/doc/api/api_resources.md
index b14d28d6ec0..ce07bdd2966 100644
--- a/doc/api/api_resources.md
+++ b/doc/api/api_resources.md
@@ -167,7 +167,8 @@ The following API resources are available outside of project and group contexts
 | [Sidekiq metrics](sidekiq_metrics.md) **(FREE SELF)** | `/sidekiq`                                                           |
 | [Suggestions](suggestions.md)                      | `/suggestions`                                                          |
 | [System hooks](system_hooks.md)                    | `/hooks`                                                                |
-| [To-dos](todos.md)                                  | `/todos`                                                                |
+| [To-dos](todos.md)                                 | `/todos`                                                                |
+| [Usage data](usage_data.md)                        | `/usage_data` (For GitLab instance [Administrator](../user/permissions.md) users only) |
 | [Users](users.md)                                  | `/users`                                                                |
 | [Validate `.gitlab-ci.yml` file](lint.md)          | `/lint`                                                                 |
 | [Version](version.md)                              | `/version`                                                              |
diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index 2bef0260565..c803c888449 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -631,7 +631,7 @@ Parsed field from an alert used for custom mappings.
 | Field | Type | Description |
 | ----- | ---- | ----------- |
 | `label` | [`String`](#string) | Human-readable label of the payload path. |
-| `path` | [`[String!]`](#string) | Path to value inside payload JSON. |
+| `path` | [`[PayloadAlertFieldPathSegment!]`](#payloadalertfieldpathsegment) | Path to value inside payload JSON. |
 | `type` | [`AlertManagementPayloadAlertFieldType`](#alertmanagementpayloadalertfieldtype) | Type of the parsed value. |
 
 ### `AlertManagementPayloadAlertMappingField`
@@ -642,7 +642,7 @@ Parsed field (with its name) from an alert used for custom mappings.
 | ----- | ---- | ----------- |
 | `fieldName` | [`AlertManagementPayloadAlertFieldName`](#alertmanagementpayloadalertfieldname) | A GitLab alert field name. |
 | `label` | [`String`](#string) | Human-readable label of the payload path. |
-| `path` | [`[String!]`](#string) | Path to value inside payload JSON. |
+| `path` | [`[PayloadAlertFieldPathSegment!]`](#payloadalertfieldpathsegment) | Path to value inside payload JSON. |
 | `type` | [`AlertManagementPayloadAlertFieldType`](#alertmanagementpayloadalertfieldtype) | Type of the parsed value. |
 
 ### `AlertManagementPrometheusIntegration`
@@ -4827,6 +4827,7 @@ Information about pagination in a connection.
 | `startedAt` | [`Time`](#time) | Timestamp when the pipeline was started. |
 | `status` | [`PipelineStatusEnum!`](#pipelinestatusenum) | Status of the pipeline (CREATED, WAITING_FOR_RESOURCE, PREPARING, PENDING, RUNNING, FAILED, SUCCESS, CANCELED, SKIPPED, MANUAL, SCHEDULED). |
 | `testReportSummary` | [`TestReportSummary!`](#testreportsummary) | Summary of the test report generated by the pipeline. |
+| `testSuite` | [`TestSuite`](#testsuite) | A specific test suite in a pipeline test report. |
 | `updatedAt` | [`Time!`](#time) | Timestamp of the pipeline's last activity. |
 | `upstream` | [`Pipeline`](#pipeline) | Pipeline that triggered the pipeline. |
 | `user` | [`User`](#user) | Pipeline user. |
@@ -5276,6 +5277,15 @@ Represents rules that commit pushes must follow.
 | ----- | ---- | ----------- |
 | `rejectUnsignedCommits` | [`Boolean!`](#boolean) | Indicates whether commits not signed through GPG will be rejected. |
 
+### `RecentFailures`
+
+Recent failure history of a test case.
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `baseBranch` | [`String`](#string) | Name of the base branch of the project. |
+| `count` | [`Int`](#int) | Number of times the test case has failed in the past 14 days. |
+
 ### `Release`
 
 Represents a release.
@@ -5522,13 +5532,44 @@ Autogenerated return type of RepositionImageDiffNote.
 
 | Field | Type | Description |
 | ----- | ---- | ----------- |
-| `blobs` | [`BlobConnection`](#blobconnection) | Blobs contained within the repository. |
+| `blobs` | [`RepositoryBlobConnection`](#repositoryblobconnection) | Blobs contained within the repository. |
 | `branchNames` | [`[String!]`](#string) | Names of branches available in this repository that match the search pattern. |
 | `empty` | [`Boolean!`](#boolean) | Indicates repository has no visible content. |
 | `exists` | [`Boolean!`](#boolean) | Indicates a corresponding Git repository exists on disk. |
 | `rootRef` | [`String`](#string) | Default branch of the repository. |
 | `tree` | [`Tree`](#tree) | Tree of the repository. |
 
+### `RepositoryBlob`
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `id` | [`ID!`](#id) | ID of the blob. |
+| `lfsOid` | [`String`](#string) | LFS OID of the blob. |
+| `mode` | [`String`](#string) | Blob mode. |
+| `name` | [`String`](#string) | Blob name. |
+| `oid` | [`String!`](#string) | OID of the blob. |
+| `path` | [`String!`](#string) | Path of the blob. |
+| `webPath` | [`String`](#string) | Web path of the blob. |
+
+### `RepositoryBlobConnection`
+
+The connection type for RepositoryBlob.
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `edges` | [`[RepositoryBlobEdge]`](#repositoryblobedge) | A list of edges. |
+| `nodes` | [`[RepositoryBlob]`](#repositoryblob) | A list of nodes. |
+| `pageInfo` | [`PageInfo!`](#pageinfo) | Information to aid in pagination. |
+
+### `RepositoryBlobEdge`
+
+An edge in a connection.
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `cursor` | [`String!`](#string) | A cursor for use in pagination. |
+| `node` | [`RepositoryBlob`](#repositoryblob) | The item at the end of the edge. |
+
 ### `Requirement`
 
 Represents a requirement.
@@ -6333,6 +6374,42 @@ An edge in a connection.
 | `cursor` | [`String!`](#string) | A cursor for use in pagination. |
 | `node` | [`TerraformStateVersionRegistry`](#terraformstateversionregistry) | The item at the end of the edge. |
 
+### `TestCase`
+
+Test case in pipeline test report.
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `attachmentUrl` | [`String`](#string) | URL of the test case attachment file. |
+| `classname` | [`String`](#string) | Classname of the test case. |
+| `executionTime` | [`Float`](#float) | Test case execution time in seconds. |
+| `file` | [`String`](#string) | Path to the file of the test case. |
+| `name` | [`String`](#string) | Name of the test case. |
+| `recentFailures` | [`RecentFailures`](#recentfailures) | Recent failure history of the test case on the base branch. |
+| `stackTrace` | [`String`](#string) | Stack trace of the test case. |
+| `status` | [`TestCaseStatus`](#testcasestatus) | Status of the test case (error, failed, success, skipped). |
+| `systemOutput` | [`String`](#string) | System output of the test case. |
+
+### `TestCaseConnection`
+
+The connection type for TestCase.
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `count` | [`Int!`](#int) | Total count of collection. |
+| `edges` | [`[TestCaseEdge]`](#testcaseedge) | A list of edges. |
+| `nodes` | [`[TestCase]`](#testcase) | A list of nodes. |
+| `pageInfo` | [`PageInfo!`](#pageinfo) | Information to aid in pagination. |
+
+### `TestCaseEdge`
+
+An edge in a connection.
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `cursor` | [`String!`](#string) | A cursor for use in pagination. |
+| `node` | [`TestCase`](#testcase) | The item at the end of the edge. |
+
 ### `TestReport`
 
 Represents a requirement test report.
@@ -6386,6 +6463,22 @@ Total test report statistics.
 | `suiteError` | [`String`](#string) | Test suite error message. |
 | `time` | [`Float`](#float) | Total duration of the tests. |
 
+### `TestSuite`
+
+Test suite in a pipeline test report.
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `errorCount` | [`Int`](#int) | Total number of test cases that had an error. |
+| `failedCount` | [`Int`](#int) | Total number of test cases that failed in the test suite. |
+| `name` | [`String`](#string) | Name of the test suite. |
+| `skippedCount` | [`Int`](#int) | Total number of test cases that were skipped in the test suite. |
+| `successCount` | [`Int`](#int) | Total number of test cases that succeeded in the test suite. |
+| `suiteError` | [`String`](#string) | Test suite error message. |
+| `testCases` | [`TestCaseConnection`](#testcaseconnection) | Test cases in the test suite. |
+| `totalCount` | [`Int`](#int) | Total number of the test cases in the test suite. |
+| `totalTime` | [`Float`](#float) | Total duration of the tests in the test suite. |
+
 ### `TestSuiteSummary`
 
 Test suite summary in a pipeline test report.
@@ -8424,6 +8517,15 @@ Common sort values.
 | `updated_asc` **{warning-solid}** | **Deprecated:** This was renamed. Please use `UPDATED_ASC`. Deprecated in 13.5. |
 | `updated_desc` **{warning-solid}** | **Deprecated:** This was renamed. Please use `UPDATED_DESC`. Deprecated in 13.5. |
 
+### `TestCaseStatus`
+
+| Value | Description |
+| ----- | ----------- |
+| `error` | Test case that has a status of error. |
+| `failed` | Test case that has a status of failed. |
+| `skipped` | Test case that has a status of skipped. |
+| `success` | Test case that has a status of success. |
+
 ### `TestReportState`
 
 State of a test report.
@@ -8967,6 +9069,10 @@ A `PackagesPackageID` is a global ID. It is encoded as a string.
 
 An example `PackagesPackageID` is: `"gid://gitlab/Packages::Package/1"`.
 
+### `PayloadAlertFieldPathSegment`
+
+String or integer.
+
 ### `ProjectID`
 
 A `ProjectID` is a global ID. It is encoded as a string.
diff --git a/doc/api/usage_data.md b/doc/api/usage_data.md
index 671e60be587..024caa96565 100644
--- a/doc/api/usage_data.md
+++ b/doc/api/usage_data.md
@@ -5,17 +5,61 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference, api
 ---
 
-# UsageData API **(FREE SELF)**
+# Usage Data API **(FREE SELF)**
 
-The UsageData API, associated with [Usage Ping](../development/usage_ping/index.md), is available only for
-the use of GitLab instance [Administrator](../user/permissions.md) users.
+The Usage Data API is associated with [Usage Ping](../development/usage_ping/index.md).
 
-## UsageDataQueries API
+## Export metric definitions as a single YAML file
+
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/57270) in GitLab 13.11.
+
+Export all metric definitions as a single YAML file, similar to the [Metrics Dictionary](../development/usage_ping/dictionary.md), for easier importing.
+
+```plaintext
+GET /usage_data/metric_definitions
+```
+
+Example request:
+
+```shell
+curl "https://gitlab.example.com/api/v4/usage_data/metric_definitions"
+```
+
+Example response:
+
+```yaml
+---
+- key_path: redis_hll_counters.search.i_search_paid_monthly
+  description: Calculated unique users to perform a search with a paid license enabled
+    by month
+  product_section: enablement
+  product_stage: enablement
+  product_group: group::global search
+  product_category: global_search
+  value_type: number
+  status: data_available
+  time_frame: 28d
+  data_source: redis_hll
+  distribution:
+  - ee
+  tier:
+  - premium
+  - ultimate
+...
+```
+
+## Export Usage Ping SQL queries
+
+This action is available only for the GitLab instance [Administrator](../user/permissions.md) users.
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/57016) in GitLab 13.11.
 > - [Deployed behind a feature flag](../user/feature_flags.md), disabled by default.
 
-Return all of the raw SQL queries used to compute usage ping.
+Return all of the raw SQL queries used to compute Usage Ping.
+
+```plaintext
+GET /usage_data/queries
+```
 
 Example request:
 
@@ -23,7 +67,7 @@ Example request:
 curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/usage_data/queries"
 ```
 
-Sample response
+Example response:
 
 ```json
 {
diff --git a/doc/development/usage_ping/index.md b/doc/development/usage_ping/index.md
index 4b584c6ecc9..a62b58d6095 100644
--- a/doc/development/usage_ping/index.md
+++ b/doc/development/usage_ping/index.md
@@ -1411,37 +1411,6 @@ bin/rake gitlab:usage_data:dump_sql_in_json
 bin/rake gitlab:usage_data:dump_sql_in_yaml > ~/Desktop/usage-metrics-2020-09-02.yaml
 ```
 
-## Export metric definitions as a single YAML file
-
-Use this API endpoint to export all metric definitions as a single YAML file, similar to the [Metrics Dictionary](dictionary.md), for easier importing.
-
-```plaintext
-GET /usage_data/metric_definitions
-```
-
-Response
-
-```yaml
----
-- key_path: redis_hll_counters.search.i_search_paid_monthly
-  description: Calculated unique users to perform a search with a paid license enabled
-    by month
-  product_section: enablement
-  product_stage: enablement
-  product_group: group::global search
-  product_category: global_search
-  value_type: number
-  status: data_available
-  time_frame: 28d
-  data_source: redis_hll
-  distribution:
-  - ee
-  tier:
-  - premium
-  - ultimate
-...
-```
-
 ## Generating and troubleshooting usage ping
 
 This activity is to be done via a detached screen session on a remote server.
diff --git a/doc/integration/jira/connect-app.md b/doc/integration/jira/connect-app.md
index fa0df27585e..667fa9e6b19 100644
--- a/doc/integration/jira/connect-app.md
+++ b/doc/integration/jira/connect-app.md
@@ -11,6 +11,8 @@ You can integrate GitLab.com and Jira Cloud using the
 app in the Atlassian Marketplace. The user configuring GitLab for Jira must have
 [Maintainer](../../user/permissions.md) permissions in the GitLab namespace.
 
+This integration method supports [smart commits](dvcs.md#smart-commits).
+
 This method is recommended when using GitLab.com and Jira Cloud because data is
 synchronized in real-time. The DVCS connector updates data only once per hour.
 If you are not using both of these environments, use the [Jira DVCS Connector](dvcs.md) method.
diff --git a/doc/integration/jira/dvcs.md b/doc/integration/jira/dvcs.md
index 1d67dab9a84..ce80d370627 100644
--- a/doc/integration/jira/dvcs.md
+++ b/doc/integration/jira/dvcs.md
@@ -18,6 +18,25 @@ are accessible.
 - **Jira Cloud**: Your instance must be accessible through the internet.
 - **Jira Server**: Your network must allow access to your instance.
 
+## Smart commits
+
+When connecting GitLab with Jira with DVCS, you can process your Jira issues using
+special commands, called
+[Smart Commits](https://support.atlassian.com/jira-software-cloud/docs/process-issues-with-smart-commits/),
+in your commit messages. With Smart Commits, you can:
+
+- Comment on issues.
+- Record time-tracking information against issues.
+- Transition issues to any status defined in the Jira project's workflow.
+
+Commands must be in the first line of the commit message. The
+[Jira Software documentation](https://support.atlassian.com/jira-software-cloud/docs/process-issues-with-smart-commits/)
+contains more information about how smart commits work, and what commands are available
+for your use.
+
+For smart commits to work, the committing user on GitLab must have a corresponding
+user on Jira with the same email address or username.
+
 ## Configure a GitLab application for DVCS
 
 We recommend you create and use a `jira` user in GitLab, and use the account only
diff --git a/doc/user/clusters/agent/index.md b/doc/user/clusters/agent/index.md
index 0ad2972c5a8..31accfdd9e4 100644
--- a/doc/user/clusters/agent/index.md
+++ b/doc/user/clusters/agent/index.md
@@ -8,9 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/223061) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.4.
 > - [In GitLab 13.10](https://gitlab.com/gitlab-org/gitlab/-/issues/300960), KAS became available on GitLab.com under `wss://kas.gitlab.com` through an Early Adopter Program.
-
-WARNING:
-This feature might not be available to you. Check the **version history** note above for details.
+> - Introduced in GitLab 13.11, the GitLab Kubernetes Agent became available to every project on GitLab.com.
 
 The [GitLab Kubernetes Agent](https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent)
 is an active in-cluster component for solving GitLab and Kubernetes integration
@@ -169,17 +167,21 @@ the Agent in subsequent steps. You can create an Agent record with GraphQL:
 
 ### Install the Agent into the cluster
 
-Next, install the in-cluster component of the Agent.
+To install the in-cluster component of the Agent, first you need to define a namespace. To create a new namespace,
+for example, `gitlab-kubernetes-agent`, run:
 
-NOTE:
-For GitLab.com users, the KAS is available at `wss://kas.gitlab.com`.
+```shell
+kubectl create namespace gitlab-kubernetes-agent
+```
 
-#### One-liner installation
+To perform a one-liner installation, run the command below. Make sure to replace:
 
-Replace the value of `agent-token` below with the token received from the previous step. Also, replace `kas-address` with the configured access of the Kubernetes Agent Server:
+- `your-agent-token` with the token received from the previous step.
+- `gitlab-kubernetes-agent` with the namespace you defined in the previous step.
+- `wss://kas.gitlab.example.com` with the configured access of the Kubernetes Agent Server (KAS). For GitLab.com users, the KAS is available under `wss://kas.gitlab.com`.
 
 ```shell
-docker run --pull=always --rm registry.gitlab.com/gitlab-org/cluster-integration/gitlab-agent/cli:stable generate --agent-token=your-agent-token --kas-address=wss://kas.gitlab.example.com --agent-version stable | kubectl apply -f -
+docker run --pull=always --rm registry.gitlab.com/gitlab-org/cluster-integration/gitlab-agent/cli:stable generate --agent-token=your-agent-token --kas-address=wss://kas.gitlab.example.com --agent-version stable --namespace gitlab-kubernetes-agent | kubectl apply -f -
 ```
 
 Set `--agent-version` to the latest released patch version matching your
@@ -206,17 +208,11 @@ Otherwise, you can follow below for fully manual, detailed installation steps.
 
 After generating the token, you must apply it to the Kubernetes cluster.
 
-1. If you haven't previously defined or created a namespace, run the following command:
+To create your Secret, run:
 
-   ```shell
-   kubectl create namespace <YOUR-DESIRED-NAMESPACE>
-   ```
-
-1. Run the following command to create your Secret:
-
-   ```shell
-   kubectl create secret generic -n <YOUR-DESIRED-NAMESPACE> gitlab-agent-token --from-literal=token='YOUR_AGENT_TOKEN'
-   ```
+```shell
+kubectl create secret generic -n <YOUR_NAMESPACE> gitlab-agent-token --from-literal=token='YOUR_AGENT_TOKEN'
+```
 
 The following example file contains the
 Kubernetes resources required for the Agent to be installed. You can modify this
diff --git a/doc/user/project/integrations/webhooks.md b/doc/user/project/integrations/webhooks.md
index dc63a32ed10..56a339e02d2 100644
--- a/doc/user/project/integrations/webhooks.md
+++ b/doc/user/project/integrations/webhooks.md
@@ -1311,7 +1311,6 @@ X-Gitlab-Event: Job Hook
     "name": "User",
     "email": "user@gitlab.com",
     "avatar_url": "http://www.gravatar.com/avatar/e32bd13e2add097461cb96824b7a829c?s=80\u0026d=identicon",
-    "email": "admin@example.com"
   },
   "commit": {
     "id": 2366,
diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md
index 58e80504212..3a5a581198b 100644
--- a/doc/user/project/merge_requests/creating_merge_requests.md
+++ b/doc/user/project/merge_requests/creating_merge_requests.md
@@ -172,6 +172,9 @@ create a merge request from your fork to contribute back to the main project:
 1. In the left menu, go to **Merge Requests**, and click **New Merge Request**.
 1. In the **Source branch** drop-down list box, select your branch in your forked repository as the source branch.
 1. In the **Target branch** drop-down list box, select the branch from the upstream repository as the target branch.
+   You can set a [default target project](#set-the-default-target-project) to
+   change the default target branch (which can be useful when working with a
+   forked project).
 1. After entering the credentials, click **Compare branches and continue** to compare your local changes to the upstream repository.
 1. Assign a user to review your changes, and click **Submit merge request**.
 
@@ -183,6 +186,24 @@ fork from its upstream project in the **Settings > Advanced Settings** section b
 
 For further details, [see the forking workflow documentation](../repository/forking_workflow.md).
 
+## Set the default target project
+
+Merge requests have a source and a target project which are the same, unless
+forking is involved. Creating a fork of the project can cause either of these
+scenarios when you create a new merge request:
+
+- You target an upstream project (the project you forked, and the default
+  option).
+- You target your own fork.
+
+If you want to have merge requests from a fork by default target your own fork
+(instead of the upstream project), you can change the default by:
+
+1. In your project, go to **Settings > General > Merge requests**.
+1. In the **Target project** section, select the option you want to use for
+   your default target project.
+1. Select **Save changes**.
+
 ## New merge request by email **(FREE SELF)**
 
 _This feature needs [incoming email](../../../administration/incoming_email.md)
diff --git a/doc/user/project/settings/index.md b/doc/user/project/settings/index.md
index bcfd7f5e5d9..6d37d26f6e8 100644
--- a/doc/user/project/settings/index.md
+++ b/doc/user/project/settings/index.md
@@ -214,6 +214,7 @@ Set up your project's merge request settings:
 - Enable [merge only when all threads are resolved](../../discussions/index.md#only-allow-merge-requests-to-be-merged-if-all-threads-are-resolved).
 - Enable [`delete source branch after merge` option by default](../merge_requests/getting_started.md#deleting-the-source-branch)
 - Configure [suggested changes commit messages](../../discussions/index.md#configure-the-commit-message-for-applied-suggestions)
+- Configure [the default target project](../merge_requests/creating_merge_requests.md#set-the-default-target-project) for merge requests coming from forks.
 
 ### Service Desk