Add latest changes from gitlab-org/gitlab@master

14 files changed, 248 insertions, 72 deletions

diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index 1b356fea17c..7eb816bf985 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -2175,6 +2175,25 @@ Input type: `EscalationPolicyCreateInput`
 | <a id="mutationescalationpolicycreateerrors"></a>`errors` | [`[String!]!`](#string) | Errors encountered during execution of the mutation. |
 | <a id="mutationescalationpolicycreateescalationpolicy"></a>`escalationPolicy` | [`EscalationPolicyType`](#escalationpolicytype) | The escalation policy. |
 
+### `Mutation.escalationPolicyDestroy`
+
+Input type: `EscalationPolicyDestroyInput`
+
+#### Arguments
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| <a id="mutationescalationpolicydestroyclientmutationid"></a>`clientMutationId` | [`String`](#string) | A unique identifier for the client performing the mutation. |
+| <a id="mutationescalationpolicydestroyid"></a>`id` | [`IncidentManagementEscalationPolicyID!`](#incidentmanagementescalationpolicyid) | The escalation policy internal ID to remove. |
+
+#### Fields
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| <a id="mutationescalationpolicydestroyclientmutationid"></a>`clientMutationId` | [`String`](#string) | A unique identifier for the client performing the mutation. |
+| <a id="mutationescalationpolicydestroyerrors"></a>`errors` | [`[String!]!`](#string) | Errors encountered during execution of the mutation. |
+| <a id="mutationescalationpolicydestroyescalationpolicy"></a>`escalationPolicy` | [`EscalationPolicyType`](#escalationpolicytype) | The escalation policy. |
+
 ### `Mutation.exportRequirements`
 
 Input type: `ExportRequirementsInput`
diff --git a/doc/development/changelog.md b/doc/development/changelog.md
index 8e7b9868cbe..616b175c9eb 100644
--- a/doc/development/changelog.md
+++ b/doc/development/changelog.md
@@ -79,8 +79,17 @@ EE: true
 
 ## What warrants a changelog entry?
 
-- Any user-facing change **should** have a changelog entry. Example: "GitLab now
+- Any change that introduces a database migration, whether it's regular, post,
+  or data migration, **must** have a changelog entry, even if it is behind a
+  disabled feature flag. 
+- [Security fixes](https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/developer.md)
+  **must** have a changelog entry, with `Changelog` trailer set to `security`.
+- Any user-facing change **must** have a changelog entry. Example: "GitLab now
   uses system fonts for all text."
+- Any client-facing change to our REST and GraphQL APIs **must** have a changelog entry.
+  See the [complete list what comprises a GraphQL breaking change](api_graphql_styleguide.md#breaking-changes).
+- Any change that introduces an [Advanced Search migration](elasticsearch.md#creating-a-new-advanced-search-migration)
+  **must** have a changelog entry.
 - A fix for a regression introduced and then fixed in the same release (such as
   fixing a bug introduced during a monthly release candidate) **should not**
   have a changelog entry.
diff --git a/doc/topics/build_your_application.md b/doc/topics/build_your_application.md
new file mode 100644
index 00000000000..d084ecec435
--- /dev/null
+++ b/doc/topics/build_your_application.md
@@ -0,0 +1,16 @@
+---
+stage: 
+group: 
+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
+---
+
+# Build your application **(FREE)**
+
+Add your source code to a repository, create merge requests to check in
+code, and use CI/CD to generate your application. Include packages in your app and output it to a variety of environments.
+
+- [Repositories](../user/project/repository/index.md)
+- [Merge requests](../user/project/merge_requests/index.md)
+- [CI/CD](../ci/README.md)
+- [Packages & Registries](../user/packages/index.md)
+- [Application infrastructure](../user/project/clusters/index.md)
diff --git a/doc/topics/git/lfs/index.md b/doc/topics/git/lfs/index.md
index 0851d3f6b50..ff5cfe0ac3e 100644
--- a/doc/topics/git/lfs/index.md
+++ b/doc/topics/git/lfs/index.md
@@ -161,6 +161,34 @@ Feature.disable(:include_lfs_blobs_in_archive)
 
 ## Troubleshooting
 
+### Encountered `n` file(s) that should have been pointers, but weren't
+
+This error indicates the file (or files) are expected to be tracked by LFS, but for
+some reason the repository is not tracking them as LFS. This issue can be one
+potential reason for this error:
+[Files not tracked with LFS when uploaded through the web interface](https://gitlab.com/gitlab-org/gitlab/-/issues/326342#note_586820485)
+
+To resolve the problem, migrate the affected file (or files) and push back to the repository:
+
+1. Migrate the file to LFS:
+
+   ```shell
+   git lfs migrate import --yes --no-rewrite "<your-file>"
+   ```
+
+1. Push back to your repository:
+
+   ```shell
+   git push
+   ```
+
+1. (Optional) Clean up your `.git` folder:
+
+   ```shell
+   git reflog expire --expire-unreachable=now --all
+   git gc --prune=now
+   ```
+
 ### error: Repository or object not found
 
 There are a couple of reasons why this error can occur:
diff --git a/doc/topics/plan_and_track.md b/doc/topics/plan_and_track.md
new file mode 100644
index 00000000000..662898e88fc
--- /dev/null
+++ b/doc/topics/plan_and_track.md
@@ -0,0 +1,28 @@
+---
+stage: 
+group: 
+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
+---
+
+# Plan and track work **(FREE)**
+
+Plan your work by creating requirements, issues, and epics. Schedule work
+with milestones and track your team's time. Learn how to save time with
+quick actions, see how GitLab renders Markdown text, and learn how to
+use Git to interact with GitLab.
+
+- [Epics](../user/group/epics/index.md)
+- [Issues](../user/project/issues/index.md)
+- [Labels](../user/project/labels.md)
+- [Discussions](../user/discussions/index.md)
+- [Iterations](../user/group/iterations/index.md)
+- [Milestones](../user/project/milestones/index.md)
+- [Requirements](../user/project/requirements/index.md)
+- [Roadmaps](../user/group/roadmap/index.md)
+- [Time tracking](../user/project/time_tracking.md)
+- [Wikis](../user/project/wiki/index.md)
+- [Keyboard shortcuts](../user/shortcuts.md)
+- [Quick actions](../user/project/quick_actions.md)
+- [Markdown](../user/markdown.md)
+- [To-Do lists](../user/todos.md)
+- [Using Git](../topics/git/index.md)
diff --git a/doc/topics/release_your_application.md b/doc/topics/release_your_application.md
new file mode 100644
index 00000000000..31eb7705760
--- /dev/null
+++ b/doc/topics/release_your_application.md
@@ -0,0 +1,13 @@
+---
+stage: 
+group: 
+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
+---
+
+# Release your application **(FREE)**
+
+Release your application internally or to the public. Use
+flags to release features incrementally.
+
+- [Releases](../user/project/releases/index.md)
+- [Feature flags](../operations/feature_flags.md)
diff --git a/doc/topics/set_up_organization.md b/doc/topics/set_up_organization.md
new file mode 100644
index 00000000000..d8b1ab59b9e
--- /dev/null
+++ b/doc/topics/set_up_organization.md
@@ -0,0 +1,16 @@
+---
+stage: 
+group: 
+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
+---
+
+# Set up your organization **(FREE)**
+
+Configure your organization and its users. Determine user roles
+and give everyone access to the projects they need.
+
+- [Members](../user/project/members/index.md)
+- [Groups](../user/group/index.md)
+- [User account options](../user/profile/index.md)
+- [SSH keys](../ssh/README.md)
+- [GitLab.com settings](../user/gitlab_com/index.md)
diff --git a/doc/topics/use_gitlab.md b/doc/topics/use_gitlab.md
new file mode 100644
index 00000000000..f45dc91131c
--- /dev/null
+++ b/doc/topics/use_gitlab.md
@@ -0,0 +1,19 @@
+---
+stage: 
+group: 
+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
+---
+
+# Use GitLab **(FREE)**
+
+Get to know the GitLab end-to-end workflow. Configure permissions,
+organize your work, create and secure your application, and analyze its performance. Report on team productivity throughout the process.
+
+- [Set up your organization](set_up_organization.md)
+- [Organize work with projects](../user/project/index.md)
+- [Plan and track work](plan_and_track.md)
+- [Build your application](build_your_application.md)
+- [Secure your application](../user/application_security/index.md)
+- [Release your application](release_your_application.md)
+- [Monitor application performance](../operations/index.md)
+- [Analyze GitLab usage](../user/analytics/index.md)
diff --git a/doc/user/analytics/index.md b/doc/user/analytics/index.md
index d50a183aa54..8c67163c4b0 100644
--- a/doc/user/analytics/index.md
+++ b/doc/user/analytics/index.md
@@ -4,7 +4,7 @@ group: Optimize
 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
 ---
 
-# Analytics **(FREE)**
+# Analyze GitLab usage **(FREE)**
 
 ## Definitions
 
diff --git a/doc/user/analytics/value_stream_analytics.md b/doc/user/analytics/value_stream_analytics.md
index 2af98492ee7..c311317b909 100644
--- a/doc/user/analytics/value_stream_analytics.md
+++ b/doc/user/analytics/value_stream_analytics.md
@@ -7,7 +7,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 # Value Stream Analytics **(FREE)**
 
 > - Introduced as Cycle Analytics prior to GitLab 12.3 at the project level.
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/12077) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.3 at the group level.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/12077) in GitLab Premium 12.3 at the group level.
 > - [Renamed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/23427) from Cycle Analytics to Value Stream Analytics in GitLab 12.8.
 
 Value Stream Analytics measures the time spent to go from an
@@ -15,20 +15,20 @@ Value Stream Analytics measures the time spent to go from an
 (also known as cycle time) for each of your projects or groups. Value Stream Analytics displays the median time
 spent in each stage defined in the process.
 
-Value Stream Analytics is useful in order to quickly determine the velocity of a given
+You can use Value Stream Analytics to determine the velocity of a given
 project. It points to bottlenecks in the development process, enabling management
 to uncover, triage, and identify the root cause of slowdowns in the software development life cycle.
 
-For information on how to contribute to the development of Value Stream Analytics, see our [contributor documentation](../../development/value_stream_analytics.md).
+For information about how to contribute to the development of Value Stream Analytics, see our [contributor documentation](../../development/value_stream_analytics.md).
 
-Project-level Value Stream Analytics is available via **Project > Analytics > Value Stream**.
+Project-level Value Stream Analytics is available by using **Project > Analytics > Value Stream**.
 
 NOTE:
 [Group-level Value Stream Analytics](../group/value_stream_analytics) is also available.
 
 ## Default stages
 
-The stages tracked by Value Stream Analytics by default represent the [GitLab flow](../../topics/gitlab_flow.md). These stages can be customized in Group Level Value Stream Analytics.
+The stages tracked by Value Stream Analytics by default represent the [GitLab flow](../../topics/gitlab_flow.md). You can customize these stages in group-level Value Stream Analytics.
 
 - **Issue** (Tracker)
   - Time to schedule an issue (by milestone or by adding it to an issue board)
@@ -38,55 +38,51 @@ The stages tracked by Value Stream Analytics by default represent the [GitLab fl
   - Time to create a merge request
 - **Test** (CI)
   - Time it takes GitLab CI/CD to test your code
-- **Review** (Merge Request/MR)
+- **Review** (Merge request)
   - Time spent on code review
 - **Staging** (Continuous Deployment)
   - Time between merging and deploying to production
 
 ### Date ranges
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/36300) in GitLab 10.0.
+To filter analytics results based on a date range, select one of these options:
 
-GitLab provides the ability to filter analytics based on a date range. To filter results, select one of these options:
-
-1. Last 7 days
-1. Last 30 days (default)
-1. Last 90 days
+- **Last 7 days**
+- **Last 30 days** (default)
+- **Last 90 days**
 
 ## How Time metrics are measured
 
-The "Time" metrics near the top of the page are measured as follows:
+The **Time** metrics near the top of the page are measured as follows:
 
-- **Lead time**: median time from issue created to issue closed.
-- **Cycle time**: median time from first commit to issue closed. (You can associate a commit with an issue by [crosslinking in the commit message](../project/issues/crosslinking_issues.md#from-commit-messages).)
+- **Lead time**: Median time from issue created to issue closed.
+- **Cycle time**: Median time from first commit to issue closed. (You can associate a commit with an issue by [crosslinking in the commit message](../project/issues/crosslinking_issues.md#from-commit-messages).)
 
 ## How the stages are measured
 
-Value Stream Analytics uses start events and stop events to measure the time that an Issue or MR spends in each stage.
-For example, a stage might start when one label is added to an issue, and end when another label is added.
-Items are not included in the stage time calculation if they have not reached the stop event.
-
-Each stage of Value Stream Analytics is further described in the table below.
+Value Stream Analytics uses start events and stop events to measure the time that an issue or merge request spends in each stage.
+For example, a stage might start when one label is added to an issue and end when another label is added.
+Items aren't included in the stage time calculation if they have not reached the stop event.
 
-| **Stage** | **Description** |
-| --------- | --------------- |
-| Issue     | Measures the median time between creating an issue and taking action to solve it, by either labeling it or adding it to a milestone, whichever comes first. The label is tracked only if it already includes an [Issue Board list](../project/issue_board.md) created for it. |
-| Plan      | Measures the median time between the action you took for the previous stage, and pushing the first commit to the branch. That first branch commit triggers the separation between **Plan** and **Code**, and at least one of the commits in the branch must include the related issue number (such as `#42`). If the issue number is *not* included in a commit, that data is not included in the measurement time of the stage. |
-| Code      | Measures the median time between pushing a first commit (previous stage) and creating a merge request (MR). The process is tracked with the [issue closing pattern](../project/issues/managing_issues.md#closing-issues-automatically) in the description of the merge request. For example, if the issue is closed with `Closes #xxx`, it's assumed that `xxx` is issue number for the merge request). If there is no closing pattern, the start time is set to the create time of the first commit. |
-| Test      | Essentially the start to finish time for all pipelines. Measures the median time to run the entire pipeline for that project. Related to the time required by GitLab CI/CD to run every job for the commits pushed to that merge request, as defined in the previous stage. |
-| Review    | Measures the median time taken to review merge requests with a closing issue pattern, from creation to merge. |
-| Staging   | Measures the median time between merging the merge request (with a closing issue pattern) to the first deployment to a [production environment](#how-the-production-environment-is-identified). Data not collected without a production environment. |
+| Stage   | Description   |
+|---------|---------------|
+| Issue   | Measures the median time between creating an issue and taking action to solve it, by either labeling it or adding it to a milestone, whichever comes first. The label is tracked only if it already includes an [Issue Board list](../project/issue_board.md) created for it. |
+| Plan    | Measures the median time between the action you took for the previous stage, and pushing the first commit to the branch. That first branch commit triggers the separation between **Plan** and **Code**, and at least one of the commits in the branch must include the related issue number (such as `#42`). If the issue number is *not* included in a commit, that data is not included in the measurement time of the stage. |
+| Code    | Measures the median time between pushing a first commit (previous stage) and creating a merge request (MR). The process is tracked with the [issue closing pattern](../project/issues/managing_issues.md#closing-issues-automatically) in the description of the merge request. For example, if the issue is closed with `Closes #xxx`, it's assumed that `xxx` is issue number for the merge request). If there is no closing pattern, the start time is set to the create time of the first commit. |
+| Test    | Essentially the start to finish time for all pipelines. Measures the median time to run the entire pipeline for that project. Related to the time required by GitLab CI/CD to run every job for the commits pushed to that merge request, as defined in the previous stage. |
+| Review  | Measures the median time taken to review merge requests with a closing issue pattern, from creation to merge. |
+| Staging | Measures the median time between merging the merge request (with a closing issue pattern) to the first deployment to a [production environment](#how-the-production-environment-is-identified). Data not collected without a production environment. |
 
-How this works, behind the scenes:
+How this works:
 
 1. Issues and merge requests are grouped in pairs, where the merge request has the
    [closing pattern](../project/issues/managing_issues.md#closing-issues-automatically)
-   for the corresponding issue. Issue/merge request pairs without closing patterns are
-   **not** included.
-1. Issue/merge request pairs are filtered by the last XX days, specified through the UI
-   (default = 90 days). Pairs outside the filtered range are not included.
+   for the corresponding issue. Issue and merge request pairs without closing patterns are
+   not included.
+1. Issue and merge request pairs are filtered by the last XX days, specified through the UI
+   (default is `90` days). Pairs outside the filtered range are not included.
 1. For the remaining pairs, review information needed for stages, including
-   issue creation date, merge request merge time, and so on.
+   issue creation date and merge request merge time.
 
 In short, the Value Stream Analytics dashboard tracks data related to [GitLab flow](../../topics/gitlab_flow.md). It does not include data for:
 
@@ -97,67 +93,69 @@ In short, the Value Stream Analytics dashboard tracks data related to [GitLab fl
 
 ## How the production environment is identified
 
-Value Stream Analytics identifies production environments based on
-[the deployment tier of environments](../../ci/environments/index.md#deployment-tier-of-environments).
+Value Stream Analytics identifies production environments based on the
+[deployment tier of environments](../../ci/environments/index.md#deployment-tier-of-environments).
 
 ## Example workflow
 
-Below is a simple fictional workflow of a single cycle that happens in a
-single day passing through all seven stages. Note that if a stage does not have
-a start and a stop mark, it is not measured and hence not calculated in the median
-time. It is assumed that milestones are created and CI for testing and setting
+Here's a fictional workflow of a single cycle that happens in a
+single day, passing through all seven stages. If a stage doesn't have
+a start and a stop mark, it isn't measured and hence isn't calculated in the median
+time. It's assumed that milestones are created, and CI for testing and setting
 environments is configured.
 
 1. Issue is created at 09:00 (start of **Issue** stage).
-1. Issue is added to a milestone at 11:00 (stop of **Issue** stage / start of
+1. Issue is added to a milestone at 11:00 (stop of **Issue** stage and start of
    **Plan** stage).
-1. Start working on the issue, create a branch locally and make one commit at
+1. Start working on the issue, create a branch locally, and make one commit at
    12:00.
-1. Make a second commit to the branch which mentions the issue number at 12.30
-   (stop of **Plan** stage / start of **Code** stage).
-1. Push branch and create a merge request that contains the [issue closing pattern](../project/issues/managing_issues.md#closing-issues-automatically)
-   in its description at 14:00 (stop of **Code** stage / start of **Test** and
+1. Make a second commit to the branch that mentions the issue number at 12:30
+   (stop of **Plan** stage and start of **Code** stage).
+1. Push branch, and create a merge request that contains the [issue closing pattern](../project/issues/managing_issues.md#closing-issues-automatically)
+   in its description at 14:00 (stop of **Code** stage and start of **Test** and
    **Review** stages).
 1. The CI starts running your scripts defined in [`.gitlab-ci.yml`](../../ci/yaml/README.md) and
-   takes 5min (stop of **Test** stage).
-1. Review merge request, ensure that everything is OK and merge the merge
-   request at 19:00. (stop of **Review** stage / start of **Staging** stage).
-1. Now that the merge request is merged, a deployment to the `production`
+   takes 5 minutes (stop of **Test** stage).
+1. Review merge request, ensure that everything is okay, and then merge the merge
+   request at 19:00 (stop of **Review** stage and start of **Staging** stage).
+1. The merge request is merged, and a deployment to the `production`
    environment starts and finishes at 19:30 (stop of **Staging** stage).
 
-From the above example we see the time used for each stage:
+From the previous example we see the time used for each stage:
 
-- **Issue**: 2h (11:00 - 09:00)
-- **Plan**: 1h (12:00 - 11:00)
-- **Code**: 2h (14:00 - 12:00)
-- **Test**: 5min
-- **Review**: 5h (19:00 - 14:00)
-- **Staging**: 30min (19:30 - 19:00)
+- **Issue**: 2 hrs (09:00 to 11:00)
+- **Plan**: 1 hr (11:00 to 12:00)
+- **Code**: 2 hrs (12:00 to 14:00)
+- **Test**: 5 mins
+- **Review**: 5 hrs (14:00 to 19:00)
+- **Staging**: 30 mins (19:00 to 19:30)
 
 More information:
 
-- The above example specifies the issue number in a latter commit. The process
-  still collects analytics data for that issue.
-- The time required in the **Test** stage is not included in the overall time of
-  the cycle. It is included in the **Review** process, as every MR should be
+- Although the previous example specifies the issue number in a later commit, the process
+  still collects analytics data for the issue.
+- The time required in the **Test** stage isn't included in the overall time of
+  the cycle. The time is included in the **Review** process, as every merge request should be
   tested.
-- The example above illustrates only **one cycle** of the multiple stages. Value
+- The previous example illustrates only one cycle of the multiple stages. Value
   Stream Analytics, on its dashboard, shows the calculated median elapsed time
   for these issues.
 
 ## Permissions
 
-The current permissions on the Project-level Value Stream Analytics dashboard are:
+The permissions for the project-level Value Stream Analytics dashboard include:
 
-- Public projects - anyone can access.
-- Internal projects - any authenticated user can access.
-- Private projects - any member Guest and above can access.
+| Project type | Permissions                           |
+|--------------|---------------------------------------|
+| Public       | Anyone can access                     |
+| Internal     | Any authenticated user can access     |
+| Private      | Any member Guest and above can access |
 
 You can [read more about permissions](../../user/permissions.md) in general.
 
 ## More resources
 
-Learn more about Value Stream Analytics in the following resources:
+Learn more about Value Stream Analytics with the following resources:
 
 - [Value Stream Analytics feature page](https://about.gitlab.com/stages-devops-lifecycle/value-stream-analytics/).
 - [Value Stream Analytics feature preview](https://about.gitlab.com/blog/2016/09/16/feature-preview-introducing-cycle-analytics/).
diff --git a/doc/user/application_security/index.md b/doc/user/application_security/index.md
index 60f77ab048d..be9a3aec98e 100644
--- a/doc/user/application_security/index.md
+++ b/doc/user/application_security/index.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference, howto
 ---
 
-# Application security **(ULTIMATE)**
+# Secure your application **(ULTIMATE)**
 
 GitLab can check your application for security vulnerabilities including:
 
diff --git a/doc/user/project/clusters/index.md b/doc/user/project/clusters/index.md
index 341723a0abb..faa394baacb 100644
--- a/doc/user/project/clusters/index.md
+++ b/doc/user/project/clusters/index.md
@@ -61,6 +61,9 @@ Kubernetes version to any supported version at any time:
 
 Some GitLab features may support versions outside the range provided here.
 
+NOTE:
+[GKE Cluster creation](add_remove_clusters.md#create-new-cluster) by GitLab is currently not supported for Kubernetes 1.19+. For these versions you can create the cluster through GCP, then [Add existing cluster](add_remove_clusters.md#add-existing-cluster). See [the related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/331922) for more information.
+
 ### Adding and removing clusters
 
 See [Adding and removing Kubernetes clusters](add_remove_clusters.md) for details on how
diff --git a/doc/user/project/index.md b/doc/user/project/index.md
index d9283f623d4..df14c9d328e 100644
--- a/doc/user/project/index.md
+++ b/doc/user/project/index.md
@@ -5,7 +5,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated
 type: reference
 ---
 
-# Projects **(FREE)**
+# Organize work with projects **(FREE)**
 
 In GitLab, you can create projects to host
 your codebase. You can also use projects to track issues, plan work,
diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md
index e1b6956f873..e02a10ecfbc 100644
--- a/doc/user/project/issue_board.md
+++ b/doc/user/project/issue_board.md
@@ -583,7 +583,15 @@ When dragging issues between lists, different behavior occurs depending on the s
 
 ### Multi-select issue cards
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/18954) in GitLab 12.4.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/18954) in GitLab 12.4.
+> - [Placed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61955) behind a [feature flag](../feature_flags.md), disabled by default in GitLab 14.0.
+> - Disabled on GitLab.com.
+> - Not recommended for production use.
+> - To use in GitLab self-managed instances, ask a GitLab administrator to [enable it](#enable-or-disable-multi-selecting-issue-cards). **(FREE SELF)**
+
+This in-development feature might not be available for your use. There can be
+[risks when enabling features still in development](../feature_flags.md#risks-when-enabling-features-still-in-development).
+Refer to this feature's version history for more details.
 
 You can select multiple issue cards, then drag the group to another position within the list, or to
 another list. This makes it faster to reorder many issues at once.
@@ -685,3 +693,22 @@ To disable it:
 ```ruby
 Feature.disable(:iteration_board_lists)
 ```
+
+### Enable or disable multi-selecting issue cards **(FREE SELF)**
+
+Multi-selecting issue cards is under development and not ready for production use. It is
+deployed behind a feature flag that is **disabled by default**.
+[GitLab administrators with access to the GitLab Rails console](../../administration/feature_flags.md)
+can enable it.
+
+To enable it:
+
+```ruby
+Feature.enable(:board_multi_select)
+```
+
+To disable it:
+
+```ruby
+Feature.disable(:board_multi_select)
+```