Merge branch 'msj-linked-issues-references' into 'master'

Update docs mentions to use Linked issues

See merge request gitlab-org/gitlab!58663

doc/api/issue_links.md

@@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 ## List issue relations
 
-Get a list of a given issue's [related issues](../user/project/issues/related_issues.md),
+Get a list of a given issue's [linked issues](../user/project/issues/related_issues.md),
 sorted by the relationship creation datetime (ascending).
 Issues are filtered according to the user authorizations.
 

doc/development/code_review.md

@@ -38,7 +38,7 @@ Depending on the areas your merge request touches, it must be **approved** by on
 or more [maintainers](https://about.gitlab.com/handbook/engineering/workflow/code-review/#maintainer):
 
 For approvals, we use the approval functionality found in the merge request
-widget. For reviewers, we use the [reviewer functionality](../user/project/merge_requests/getting_started.md#reviewer) in the sidebar. 
+widget. For reviewers, we use the [reviewer functionality](../user/project/merge_requests/getting_started.md#reviewer) in the sidebar.
 Reviewers can add their approval by [approving additionally](../user/project/merge_requests/merge_request_approvals.md#adding-or-removing-an-approval).
 
 Getting your merge request **merged** also requires a maintainer. If it requires
@@ -365,7 +365,7 @@ experience, refactors the existing code). Then:
   - For non-mandatory suggestions, decorate with (non-blocking) so the author knows they can
     optionally resolve within the merge request or follow-up at a later stage.
   - There's a [Chrome/Firefox add-on](https://gitlab.com/conventionalcomments/conventional-comments-button) which you can use to apply [Conventional Comment](https://conventionalcomments.org/) prefixes.
-- Ensure there are no open dependencies. Check [related issues](../user/project/issues/related_issues.md) for blockers. Clarify with the author(s)
+- Ensure there are no open dependencies. Check [linked issues](../user/project/issues/related_issues.md) for blockers. Clarify with the author(s)
 if necessary. If blocked by one or more open MRs, set an [MR dependency](../user/project/merge_requests/merge_request_dependencies.md).
 - After a round of line notes, it can be helpful to post a summary note such as
   "Looks good to me", or "Just a couple things to address."

doc/development/documentation/styleguide/index.md

@@ -608,7 +608,7 @@ Follow these guidelines for punctuation:
 | Do not use tabs for indentation. Use spaces instead. You can configure your code editor to output spaces instead of tabs when pressing the tab key. | --- |
 | Use serial commas (_Oxford commas_) before the final _and_ or _or_ in a list of three or more items. (Tested in [`OxfordComma.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale/gitlab/OxfordComma.yml).) | _You can create new issues, merge requests, and milestones._ |
 | Always add a space before and after dashes when using it in a sentence (for replacing a comma, for example). | _You should try this - or not._ |
-| Always use lowercase after a colon.                              | _Related Issues: a way to create a relationship between issues._ |
+| Always use lowercase after a colon.                              | Linked issues: a way to create a relationship between issues._ |
 
 <!-- vale gitlab.Repetition = YES -->
 

doc/operations/feature_flags.md

@@ -394,4 +394,4 @@ end
 You can link related issues to a feature flag. In the **Linked issues** section,
 click the `+` button and input the issue reference number or the full URL of the issue.
 
-This feature is similar to the [related issues](../user/project/issues/related_issues.md) feature.
+This feature is similar to the [linked issues](../user/project/issues/related_issues.md) feature.

doc/user/application_security/index.md

@@ -228,15 +228,7 @@ If you already have an open issue, you can link to it from the vulnerability.
 To link to an existing issue:
 
 1. Open the vulnerability.
-1. In the **Related Issues** section, select the plus (**{plus}**) icon.
-1. In the text box that appears, type an issue number or paste an issue link.
-   - Type `#` followed by a number to show an autocomplete menu.
-   - You can enter multiple issues at once. Press the space bar after each issue number or link to converts them to tags.
-1. Select **Add**.
-
-To remove an issue, to the right of the issue number, select **{close}**.
-
-![Vulnerability related issues text box tags animation](img/vulnerability_related_issues_text_box_tags_v13_2.gif)
+1. [Add a linked issue](../project/issues/related_issues.md).
 
 ### Apply an automatic remediation for a vulnerability
 

doc/user/group/index.md

@@ -141,7 +141,7 @@ To remove a member from a group:
 1. From the left menu, select **Members**.
 1. Next to the member you want to remove, select **Delete**.
 1. Optional. On the **Remove member** confirmation box, select the
-  **Also unassign this user from related issues and merge requests** checkbox.
+  **Also unassign this user from linked issues and merge requests** checkbox.
 1. Select **Remove member**.
 
 ## Filter and sort members in a group

doc/user/index.md

@@ -59,7 +59,7 @@ With GitLab Enterprise Edition, you can also:
   - [Merge Request Approvals](project/merge_requests/merge_request_approvals.md).
   - [Multiple Assignees for Issues](project/issues/multiple_assignees_for_issues.md).
   - [Multiple Issue Boards](project/issue_board.md#multiple-issue-boards).
-- Create formal relationships between issues with [Related Issues](project/issues/related_issues.md).
+- Create formal relationships between issues with [linked issues](project/issues/related_issues.md).
 - Use [Burndown Charts](project/milestones/burndown_and_burnup_charts.md) to track progress during a sprint or while working on a new version of their software.
 - Leverage [Elasticsearch](../integration/elasticsearch.md) with [Advanced Search](search/advanced_search.md) for faster, more advanced code search across your entire GitLab instance.
 - [Authenticate users with Kerberos](../integration/kerberos.md).

doc/user/permissions.md

@@ -66,7 +66,7 @@ The following table depicts the various user permission levels in a project.
 | Download and browse job artifacts                 | ✓ (*3*) | ✓          | ✓           | ✓        | ✓      |
 | Create confidential issue                         | ✓       | ✓          | ✓           | ✓        | ✓      |
 | Create new issue                                  | ✓       | ✓          | ✓           | ✓        | ✓      |
-| See related issues                                | ✓       | ✓          | ✓           | ✓        | ✓      |
+| See linked issues                                 | ✓       | ✓          | ✓           | ✓        | ✓      |
 | View [Releases](project/releases/index.md)        | ✓ (*6*) | ✓          | ✓           | ✓        | ✓      |
 | View requirements **(ULTIMATE)**                  | ✓       | ✓          | ✓           | ✓        | ✓      |
 | View Insights **(ULTIMATE)**                      | ✓       | ✓          | ✓           | ✓        | ✓      |
@@ -82,7 +82,7 @@ The following table depicts the various user permission levels in a project.
 | [Set issue estimate and record time spent](project/time_tracking.md) | | ✓ | ✓         | ✓        | ✓      |
 | Lock issue threads                                |         | ✓          | ✓           | ✓        | ✓      |
 | Manage issue tracker                              |         | ✓          | ✓           | ✓        | ✓      |
-| Manage related issues                             |         | ✓          | ✓           | ✓        | ✓      |
+| Manage linked issues                              |         | ✓          | ✓           | ✓        | ✓      |
 | Manage labels                                     |         | ✓          | ✓           | ✓        | ✓      |
 | Create code snippets                              |         | ✓          | ✓           | ✓        | ✓      |
 | See a commit status                               |         | ✓          | ✓           | ✓        | ✓      |

doc/user/project/issues/crosslinking_issues.md

@@ -4,18 +4,21 @@ group: Project Management
 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
 ---
 
-# Crosslinking Issues
+# Crosslinking issues
 
-Please read through the [GitLab Issue Documentation](index.md) for an overview on GitLab Issues.
+There are several ways to mention an issue or make issues appear in each other's
+[Linked issues](related_issues.md) section.
 
-## From Commit Messages
+For more information on GitLab Issues, read the [issues documentation](index.md).
+
+## From commit messages
 
 Every time you mention an issue in your commit message, you're creating
 a relationship between the two stages of the development workflow: the
 issue itself and the first commit related to that issue.
 
 If the issue and the code you're committing are both in the same project,
-you simply add `#xxx` to the commit message, where `xxx` is the issue number.
+add `#xxx` to the commit message, where `xxx` is the issue number.
 If they are not in the same project, you can add the full URL to the issue
 (`https://gitlab.com/<username>/<projectname>/issues/<xxx>`).
 
@@ -36,11 +39,10 @@ for tracking your process with [GitLab Value Stream Analytics](https://about.git
 It measures the time taken for planning the implementation of that issue,
 which is the time between creating an issue and making the first commit.
 
-## From Related Issues
+## From linked issues
 
-Mentioning related issues in merge requests and other issues is useful
-for your team members and collaborators to know that there are opened
-issues regarding the same topic.
+Mentioning linked issues in merge requests and other issues helps your team members and
+collaborators know that there are opened issues regarding the same topic.
 
 You do that as explained above, when [mentioning an issue from a commit message](#from-commit-messages).
 
@@ -50,13 +52,13 @@ display in both issues. The same is valid when mentioning issues in [merge reque
 
 ![issue mentioned in issue](img/mention_in_issue.png)
 
-## From Merge Requests
+## From merge requests
 
 Mentioning issues in merge request comments works exactly the same way as
-they do for [related issues](#from-related-issues).
+they do for [linked issues](#from-linked-issues).
 
 When you mention an issue in a merge request description, it
-[links the issue and merge request together](#from-related-issues). Additionally,
+[links the issue and merge request together](#from-linked-issues). Additionally,
 you can also [set an issue to close automatically](managing_issues.md#closing-issues-automatically)
 as soon as the merge request is merged.
 

doc/user/project/issues/index.md

@@ -39,10 +39,10 @@ To learn how the GitLab Strategic Marketing department uses GitLab issues with [
 - [Import issues](csv_import.md)
 - [Export issues](csv_export.md)
 - [Upload designs to issues](design_management.md)
-- [Relate issues](related_issues.md)
+- [Linked issues](related_issues.md)
 - [Cross-link issues](crosslinking_issues.md)
 - [Bulk edit issues](../bulk_editing.md)
-- [Sort issue lists](sorting_issue_lists.md) 
+- [Sort issue lists](sorting_issue_lists.md)
 - [Search for issues](../../search/index.md#filtering-issue-and-merge-request-lists)
 - [Epics](../../group/epics/index.md)
 - [Issue Boards](../issue_board.md)

doc/user/project/issues/issue_data_and_actions.md

@@ -39,7 +39,7 @@ The numbers in the image correspond to the following features:
 - **15.** [Edit](#edit)
 - **16.** [Description](#description)
 - **17.** [Mentions](#mentions)
-- **18.** [Related Issues](#related-issues)
+- **18.** [Linked Issues](#linked-issues)
 - **19.** [Related Merge Requests](#related-merge-requests)
 - **20.** [Award emoji](#award-emoji)
 - **21.** [Show all activity](#show-all-activity)
@@ -205,10 +205,10 @@ in a different color, which allows you to quickly see which comments involve you
 Avoid mentioning `@all` in issues and merge requests, as it sends an email notification
 to all the members of that project's group. This might be interpreted as spam.
 
-### Related Issues
+### Linked Issues
 
-Issues that were mentioned as [related issues](related_issues.md) are listed here.
-You can also click the `+` to add more related issues.
+Issues that were mentioned as [linked issues](related_issues.md) are listed here.
+You can also click the `+` to add more linked issues.
 
 ### Related Merge Requests
 

doc/user/project/issues/related_issues.md

@@ -6,8 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Linked issues **(FREE)**
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/1797) in GitLab 9.4.
-> - The simple "relates to" relationship [moved](https://gitlab.com/gitlab-org/gitlab/-/issues/212329) to [GitLab Free](https://about.gitlab.com/pricing/) in 13.4.
+> The simple "relates to" relationship [moved](https://gitlab.com/gitlab-org/gitlab/-/issues/212329) to [GitLab Free](https://about.gitlab.com/pricing/) in 13.4.
 
 Linked issues are a bi-directional relationship between any two issues and appear in a block below
 the issue description. Issues can be across groups and projects.
@@ -52,6 +51,9 @@ them categorized so their relationships can be better understood visually.
 
 ![Related issue block](img/related_issue_block_v12_8.png)
 
+You can also add a linked issue from a commit message or the description in another issue or MR.
+[Learn more about crosslinking issues](crosslinking_issues.md).
+
 ## Remove a linked issue
 
 In the **Linked issues** section of an issue, click the remove button (**{close}**) on the