Add latest changes from gitlab-org/gitlab@master

6 files changed, 60 insertions, 6 deletions

diff --git a/doc/.vale/gitlab/BadgeCapitalization.yml b/doc/.vale/gitlab/BadgeCapitalization.yml
new file mode 100644
index 00000000000..7e68a06b4d5
--- /dev/null
+++ b/doc/.vale/gitlab/BadgeCapitalization.yml
@@ -0,0 +1,42 @@
+---
+# Verifies that badges are not lower case, which won't render properly.
+#
+# For a list of all options, see https://errata-ai.github.io/vale/styles/
+extends: existence
+message: 'Badge "%s" must be capitalized.'
+link: https://docs.gitlab.com/ee/development/documentation/styleguide.html#product-badges
+level: error
+scope: raw
+raw:
+  - '(\*\*\(Core\)\*\*|'
+  - '\*\*\(core\)\*\*|'
+  - '\*\*\(Starter\)\*\*|'
+  - '\*\*\(starter\)\*\*|'
+  - '\*\*\(Premium\)\*\*|'
+  - '\*\*\(premium\)\*\*|'
+  - '\*\*\(Ultimate\)\*\*|'
+  - '\*\*\(ultimate\)\*\*|'
+  - '\*\*\(Core Only\)\*\*|'
+  - '\*\*\(Core only\)\*\*|'
+  - '\*\*\(core only\)\*\*|'
+  - '\*\*\(Starter Only\)\*\*|'
+  - '\*\*\(Starter only\)\*\*|'
+  - '\*\*\(starter only\)\*\*|'
+  - '\*\*\(Premium Only\)\*\*|'
+  - '\*\*\(Premium only\)\*\*|'
+  - '\*\*\(premium only\)\*\*|'
+  - '\*\*\(Ultimate Only\)\*\*|'
+  - '\*\*\(Ultimate only\)\*\*|'
+  - '\*\*\(ultimate only\)\*\*|'
+  - '\*\*\(Free Only\)\*\*|'
+  - '\*\*\(Free only\)\*\*|'
+  - '\*\*\(free only\)\*\*|'
+  - '\*\*\(Bronze Only\)\*\*|'
+  - '\*\*\(Bronze only\)\*\*|'
+  - '\*\*\(bronze only\)\*\*|'
+  - '\*\*\(Silver Only\)\*\*|'
+  - '\*\*\(Silver only\)\*\*|'
+  - '\*\*\(silver only\)\*\*|'
+  - '\*\*\(Gold Only\)\*\*|'
+  - '\*\*\(Gold only\)\*\*|'
+  - '\*\*\(gold only\)\*\*)'
diff --git a/doc/user/application_security/dast/index.md b/doc/user/application_security/dast/index.md
index f4c0764ae0b..bbb551748c6 100644
--- a/doc/user/application_security/dast/index.md
+++ b/doc/user/application_security/dast/index.md
@@ -140,7 +140,7 @@ The only changes to the site should be from the DAST scanner. Be aware that any
 changes that users, scheduled tasks, database changes, code changes, other pipelines, or other scanners make to
 the site during a scan could lead to inaccurate results.
 
-### Authenticated scan
+### Authentication
 
 It's also possible to authenticate the user before performing the DAST checks:
 
diff --git a/doc/user/group/epics/img/epic_view_v12.3.png b/doc/user/group/epics/img/epic_view_v12.3.png
deleted file mode 100644
index 79758cf3d52..00000000000
--- a/doc/user/group/epics/img/epic_view_v12.3.png
+++ /dev/null
diff --git a/doc/user/group/epics/img/epic_view_v13.0.png b/doc/user/group/epics/img/epic_view_v13.0.png
new file mode 100644
index 00000000000..84fb835d6c6
--- /dev/null
+++ b/doc/user/group/epics/img/epic_view_v13.0.png
diff --git a/doc/user/group/epics/index.md b/doc/user/group/epics/index.md
index f039a21f195..e9d27fdbdd5 100644
--- a/doc/user/group/epics/index.md
+++ b/doc/user/group/epics/index.md
@@ -58,7 +58,7 @@ An epic's page contains the following tabs:
   - Hover over the total counts to see a breakdown of open and closed items.
 - **Roadmap**: a roadmap view of child epics which have start and due dates.
 
-![epic view](img/epic_view_v12.3.png)
+![epic view](img/epic_view_v13.0.png)
 
 ## Adding an issue to an epic
 
@@ -75,6 +75,7 @@ the issue is automatically unlinked from its current parent.
 
 To add an issue to an epic:
 
+1. Click the **Add** dropdown button.
 1. Click **Add an issue**.
 1. Identify the issue to be added, using either of the following methods:
    - Paste the link of the issue.
@@ -91,7 +92,7 @@ Creating an issue from an epic enables you to maintain focus on the broader cont
 
 To create an issue from an epic:
 
-1. On the epic's page, under **Epics and Issues**, click the arrow next to **Add an issue** and select **Create new issue**.
+1. On the epic's page, under **Epics and Issues**, click the **Add** dropdown button and select **Create new issue**.
 1. Under **Title**, enter the title for the new issue.
 1. From the **Project** dropdown, select the project in which the issue should be created.
 1. Click **Create issue**.
@@ -128,6 +129,7 @@ the maximum depth being 5.
 
 To add a child epic to an epic:
 
+1. Click the **Add** dropdown button.
 1. Click **Add an epic**.
 1. Identify the epic to be added, using either of the following methods:
    - Paste the link of the epic.
diff --git a/doc/user/project/issues/managing_issues.md b/doc/user/project/issues/managing_issues.md
index b68efe89cc2..290e4f81ca3 100644
--- a/doc/user/project/issues/managing_issues.md
+++ b/doc/user/project/issues/managing_issues.md
@@ -92,9 +92,17 @@ field values using query string parameters in a URL. This is useful for embeddin
 a URL in an external HTML page, and also certain scenarios where you want the user to
 create an issue with certain fields prefilled.
 
-The title, description, and description template fields can be prefilled using
-this method. You cannot pre-fill both the description and description template fields
-in the same URL (since a description template also populates the description field).
+The title, description, description template, and confidential fields can be prefilled
+using this method. You cannot pre-fill both the description and description template
+fields in the same URL (since a description template also populates the description
+field).
+
+| Field                | URL Parameter Name    | Notes                                                 |
+|----------------------|-----------------------|-------------------------------------------------------|
+| title                | `issue[title]`        |                                                       |
+| description          | `issue[description]`  |                                                       |
+| description template | `issuable_template`   |                                                       |
+| confidential         | `issue[confidential]` | Parameter value must be `true` to set to confidential |
 
 Follow these examples to form your new issue URL with prefilled fields.
 
@@ -102,6 +110,8 @@ Follow these examples to form your new issue URL with prefilled fields.
   and a pre-filled description, the URL would be `https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issue[title]=Validate%20new%20concept&issue[description]=Research%20idea`
 - For a new issue in the GitLab Community Edition project with a pre-filled title
   and a pre-filled description template, the URL would be `https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issue[title]=Validate%20new%20concept&issuable_template=Research%20proposal`
+- For a new issue in the GitLab Community Edition project with a pre-filled title,
+  a pre-filled description, and the confidential flag set, the URL would be `https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issue[title]=Validate%20new%20concept&issue[description]=Research%20idea&issue[confidential]=true`
 
 ## Moving Issues