Merge branch '294506-msj-remove-issue-data-and-actions' into 'master'

Remove Issue Data and Actions docs page

See merge request gitlab-org/gitlab!75212

doc/development/cicd/templates.md

@@ -392,6 +392,6 @@ If you're unsure if it's secure or not, you must ask security experts for cross-
 
 After your CI/CD template MR is created and labeled with `ci::templates`, DangerBot
 suggests one reviewer and one maintainer that can review your code. When your merge
-request is ready for review, please [mention](../../user/project/issues/issue_data_and_actions.md#mentions)
+request is ready for review, please [mention](../../user/discussions/index.md#mentions)
 the reviewer and ask them to review your CI/CD template changes. See details in the merge request that added
 [a DangerBot task for CI/CD template MRs](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/44688).

doc/development/contributing/index.md

@@ -129,7 +129,7 @@ The general flow of contributing to GitLab is:
 1. In the merge request's description:
    - Ensure you provide complete and accurate information.
    - Review the provided checklist.
-1. Assign the merge request (if possible) to, or [mention](../../user/project/issues/issue_data_and_actions.md#mentions),
+1. Assign the merge request (if possible) to, or [mention](../../user/discussions/index.md#mentions),
    one of the [code owners](../../user/project/code_owners.md) for the relevant project,
    and explain that you are ready for review.
 

doc/development/documentation/styleguide/word_list.md

@@ -20,7 +20,7 @@ For guidance not on this page, we defer to these style guides:
 ## `@mention`
 
 Try to avoid **`@mention`**. Say **mention** instead, and consider linking to the
-[mentions topic](../../../user/project/issues/issue_data_and_actions.md#mentions).
+[mentions topic](../../../user/discussions/index.md#mentions).
 Don't use backticks.
 
 ## above

doc/subscriptions/bronze_starter.md

@@ -39,7 +39,7 @@ the tiers are no longer mentioned in GitLab documentation:
 - Issues:
   - [Multiple assignees for issues](../user/project/issues/multiple_assignees_for_issues.md)
   - [Issue weights](../user/project/issues/issue_weight.md)
-  - [Issue histories](../user/project/issues/issue_data_and_actions.md#issue-history) contain changes to issue description
+  - Issue histories contain [changes to issue description](../user/discussions/index.md#view-description-change-history)
   - [Adding an issue to an iteration](../user/project/issues/managing_issues.md#add-an-issue-to-an-iteration)
 - [Iterations](../user/group/iterations/index.md)
 - [Kerberos integration](../integration/kerberos.md)

doc/user/award_emojis.md

@@ -10,7 +10,7 @@ When you're collaborating online, you get fewer opportunities for high-fives
 and thumbs-ups. Emoji can be awarded to [issues](project/issues/index.md), [merge requests](project/merge_requests/index.md),
 [snippets](snippets.md), and anywhere you can have a thread.
 
-![Award emoji](img/award_emoji_select.png)
+![Award emoji](img/award_emoji_select_v14_6.png)
 
 Award emoji make it much easier to give and receive feedback without a long
 comment thread.
@@ -34,11 +34,9 @@ downvotes.
 Award emoji can also be applied to individual comments when you want to
 celebrate an accomplishment or agree with an opinion.
 
-To:
+To add an award emoji:
 
-- Add an award emoji, click the smile in the top right of the comment and pick an emoji from the dropdown.
-- Remove an award emoji, click the emoji again.
+1. In the top right of the comment, select the smile (**{slight-smile}**).
+1. Select an emoji from the dropdown list.
 
-![Picking an emoji for a comment](img/award_emoji_comment_picker.png)
-
-![An award emoji has been applied to a comment](img/award_emoji_comment_awarded.png)
+To remove an award emoji, select the emoji again.

doc/user/discussions/index.md

@@ -34,6 +34,20 @@ You can create comments in places like:
 
 Each object can have as many as 5,000 comments.
 
+## Mentions
+
+You can mention a user or a group present in your GitLab instance with `@username` or
+`@groupname`. All mentioned users are notified with to-do items and emails.
+Users can change this setting for themselves in the
+[notification settings](../profile/notifications.md).
+
+You can quickly see which comments involve you, because
+mentions for yourself (the user currently signed in) are highlighted
+in a different color.
+
+Avoid mentioning `@all` in issues and merge requests, because it sends an email notification
+to all the members of that project's group. This might be interpreted as spam.
+
 ## Add a comment to a merge request diff
 
 You can add comments to a merge request diff. These comments
@@ -90,8 +104,10 @@ An icon is displayed on the image and a comment field is displayed.
 If you have ["reply by email"](../../administration/reply_by_email.md) configured,
 you can reply to comments by sending an email.
 
-- When you reply to a standard comment, another standard comment is created.
+- When you reply to a standard comment, it creates another standard comment.
 - When you reply to a threaded comment, it creates a reply in the thread.
+- When you [send an email to an issue email address](../project/issues/managing_issues.md#copy-issue-email-address),
+  it creates a standard comment.
 
 You can use [Markdown](../markdown.md) and [quick actions](../project/quick_actions.md) in your email replies.
 
@@ -145,7 +161,7 @@ For issues and merge requests with many comments, you can filter the page to sho
 
 1. Open a merge request's **Discussion** tab, or epic or issue's **Overview** tab.
 1. On the right side of the page, select from the filter:
-   - **Show all activity**: Display all user comments and system notes
+   - **Show all activity**: Display all user comments and system notes.
      (issue updates, mentions from other issues, changes to the description, and so on).
    - **Show comments only**: Display only user comments.
    - **Show history only**: Display only activity notes.
@@ -155,6 +171,27 @@ For issues and merge requests with many comments, you can filter the page to sho
 GitLab saves your preference, so it persists when you visit the same page again
 from any device you're logged into.
 
+## View description change history **(PREMIUM)**
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/10103) in GitLab 12.6.
+
+You can see changes to the description listed in the history.
+
+To compare the changes, select **Compare with previous version**.
+
+## Change activity sort order
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14588) in GitLab 12.10.
+
+You can reverse the default order and interact with the activity feed sorted by most recent items
+at the top. Your preference is saved in local storage and automatically applies to every issue,
+merge request, or epic you view.
+
+To change the activity sort order:
+
+1. Select the **Oldest first** (or **Newest first**) dropdown list.
+1. Select either oldest or newest items to be shown first.
+
 ## Assign an issue to the commenting user
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/191455) in GitLab 13.1.

doc/user/profile/notifications.md

@@ -67,7 +67,7 @@ For each project and group you can select one of the following levels:
 | Global      | Your global settings apply.                                 |
 | Watch       | Receive notifications for any activity.                     |
 | Participate | Receive notifications for threads you have participated in. |
-| On mention  | Receive notifications when you are [mentioned](../project/issues/issue_data_and_actions.md#mentions) in a comment. |
+| On mention  | Receive notifications when you are [mentioned](../discussions/index.md#mentions) in a comment. |
 | Disabled    | Receive no notifications.                                   |
 | Custom      | Receive notifications for selected events.                  |
 
@@ -203,7 +203,7 @@ In issues, merge requests, and epics, for most events, the notification is sent
 - Participants:
   - The author and assignee.
   - Authors of comments.
-  - Anyone [mentioned](../project/issues/issue_data_and_actions.md#mentions) by username in the title
+  - Anyone [mentioned](../discussions/index.md#mentions) by username in the title
     or description.
   - Anyone mentioned by username in a comment if their notification level is "Participating" or higher.
 - Watchers: users with notification level "Watch".
@@ -287,7 +287,7 @@ The participants are:
 
 - Authors of the design (can be multiple people if different authors have uploaded different versions of the design).
 - Authors of comments on the design.
-- Anyone that is [mentioned](../project/issues/issue_data_and_actions.md#mentions) in a comment on the design.
+- Anyone that is [mentioned](../discussions/index.md#mentions) in a comment on the design.
 
 ## Opt out of all GitLab emails
 

doc/user/project/issues/index.md

@@ -31,6 +31,7 @@ To learn how the GitLab Strategic Marketing department uses GitLab issues with [
 
 - [Create issues](managing_issues.md#create-a-new-issue)
 - [Create an issue from a template](../../project/description_templates.md#use-the-templates)
+- [Edit issues](managing_issues.md#edit-an-issue)
 - [Move issues](managing_issues.md#moving-issues)
 - [Close issues](managing_issues.md#closing-issues)
 - [Delete issues](managing_issues.md#deleting-issues)
@@ -40,13 +41,13 @@ To learn how the GitLab Strategic Marketing department uses GitLab issues with [
 - [Export issues](csv_export.md)
 - [Upload designs to issues](design_management.md)
 - [Linked issues](related_issues.md)
+- [Similar issues](managing_issues.md#similar-issues)
+- [Health status](managing_issues.md#health-status)
 - [Cross-link issues](crosslinking_issues.md)
-- [Bulk edit issues](../issues/managing_issues.md)
 - [Sort issue lists](sorting_issue_lists.md)
 - [Search for issues](../../search/index.md#filter-issue-and-merge-request-lists)
 - [Epics](../../group/epics/index.md)
 - [Issue boards](../issue_board.md)
 - [Issues API](../../../api/issues.md)
 - [Configure an external issue tracker](../../../integration/external-issue-tracker.md)
-- [Parts of an issue](issue_data_and_actions.md)
 - [Tasks](../../tasks.md)

doc/user/project/issues/managing_issues.md

@@ -19,9 +19,9 @@ Key actions for issues include:
 
 ## Create a new issue
 
-When you create a new issue, you are prompted to fill in the [data and fields of the issue](issue_data_and_actions.md),
-as illustrated below. If you know the values you want to assign to an issue, you can use the
-[Quick actions](../quick_actions.md) feature to input values.
+When you create a new issue, you are prompted to enter the fields of the issue.
+If you know the values you want to assign to an issue, you can use
+[quick actions](../quick_actions.md) to enter them.
 
 While creating an issue, you can associate it to an existing epic from current group by
 selecting it using **Epic** dropdown.
@@ -142,7 +142,13 @@ Follow these examples to form your new issue URL with prefilled fields.
 - 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`
 
-## Bulk edit issues at the project level
+## Edit an issue
+
+You can edit an issue's title and description.
+
+To edit an issue, select **Edit title and description** (**{pencil}**).
+
+### Bulk edit issues at the project level
 
 > - Assigning epic ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/210470) in GitLab 13.2.
 > - Editing health status [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/218395) in GitLab 13.2.
@@ -169,7 +175,7 @@ To update multiple project issues at the same time:
 1. Select the appropriate fields and their values from the sidebar.
 1. Click **Update all**.
 
-## Bulk edit issues at the group level
+### Bulk edit issues at the group level
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7249) in GitLab 12.1.
 > - Assigning epic ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/210470) in GitLab 13.2.
@@ -232,15 +238,23 @@ end; nil
 
 ## Closing issues
 
-When you decide that an issue is resolved, or no longer needed, you can close the issue
-using the close button:
+When you decide that an issue is resolved, or no longer needed, you can close the issue.
+The issue is marked as closed but is not deleted.
+
+To close an issue, you can do the following:
 
-![close issue - button](img/button_close_issue_v13_6.png)
+- Select **Close issue**:
 
-You can also close an issue from the [issue boards](../issue_board.md) by dragging an issue card
-from its list and dropping it into the **Closed** list.
+  ![close issue - button](img/button_close_issue_v13_6.png)
 
-![close issue from the issue board](img/close_issue_from_board.gif)
+- In an [issue board](../issue_board.md), drag an issue card from its list into the **Closed** list.
+
+  ![close issue from the issue board](img/close_issue_from_board.gif)
+
+### Reopen a closed issue
+
+To reopen a closed issue, select **Reopen issue**.
+A reopened issue is no different from any other open issue.
 
 ### Closing issues automatically
 
@@ -268,6 +282,9 @@ Closes #4, #6, and https://gitlab.com/<username>/<projectname>/issues/<xxx>
 For performance reasons, automatic issue closing is disabled for the very first
 push from an existing repository.
 
+Alternatively, when you [create a merge request from an issue](../merge_requests/getting_started.md#merge-requests-to-close-issues),
+it inherits the issue's milestone and labels.
+
 #### Default closing pattern
 
 When not specified, this default issue closing pattern is used:
@@ -382,6 +399,35 @@ You can also use the `/iteration`
 [quick action](../quick_actions.md#issues-merge-requests-and-epics)
 in a comment or description field.
 
+## Copy issue reference
+
+To refer to an issue elsewhere in GitLab, you can use its full URL or a short reference, which looks like
+`namespace/project-name#123`, where `namespace` is either a group or a username.
+
+To copy the issue reference to your clipboard:
+
+1. Go to the issue.
+1. On the right sidebar, next to **Reference**, select **Copy Reference** (**{copy-to-clipboard}**).
+
+You can now paste the reference into another description or comment.
+
+Read more about issue references in [GitLab-Flavored Markdown](../../markdown.md#gitlab-specific-references).
+
+## Copy issue email address
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/18816) in GitLab 13.8.
+
+You can create a comment in an issue by sending an email.
+
+To copy the issue's email address:
+
+1. Go to the issue.
+1. On the right sidebar, next to **Issue email**, select **Copy Reference** (**{copy-to-clipboard}**).
+
+Sending an email to this address creates a comment containing the email body.
+To learn more about creating comments by sending an email and the necessary configuration, see
+[Reply to a comment by sending email](../../discussions/index.md#reply-to-a-comment-by-sending-email).
+
 ## Real-time sidebar
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/17589) in GitLab 13.3. Disabled by default.
@@ -395,6 +441,24 @@ On GitLab.com, this feature is available.
 
 Assignees in the sidebar are updated in real time.
 
+## Assignee
+
+An issue can be assigned to one or [more users](multiple_assignees_for_issues.md).
+
+The assignees can be changed as often as needed. The idea is that the assignees are
+people responsible for an issue.
+When an issue is assigned to someone, it appears in their assigned issues list.
+
+If a user is not a member of a project, an issue can only be assigned to them if they create it
+themselves or another project member assigns them.
+
+To change the assignee on an issue:
+
+1. Go to your issue.
+1. On the right sidebar, in the **Assignee** section, select **Edit**.
+1. From the dropdown list, select the user to add as an assignee.
+1. Click or tap anywhere outside of the dropdown list.
+
 ## Similar issues
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22866) in GitLab 11.6.
@@ -427,3 +491,12 @@ After an issue is closed, its health status can't be edited and the **Edit** but
 until the issue is reopened.
 
 You can then see issue statuses in the issues list and the epic tree.
+
+## Publish an issue **(ULTIMATE)**
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/30906) in GitLab 13.1.
+
+If a status page application is associated with the project, you can use the `/publish`
+[quick action](../quick_actions.md) to publish the issue.
+
+For more information, see [GitLab Status Page](../../../operations/incident_management/status_page.md).

doc/user/project/issues/multiple_assignees_for_issues.md

@@ -12,8 +12,7 @@ In large teams, where there is shared ownership of an issue, it can be difficult
 to track who is working on it, who already completed their contributions, who
 didn't even start yet.
 
-In [GitLab Enterprise Edition](https://about.gitlab.com/pricing/),
-you can also select multiple assignees to an issue, making it easier to
+You can also select multiple [assignees](managing_issues.md#assignee) for an issue, making it easier to
 track, and making clearer who is accountable for it.
 
 ![multiple assignees for issues](img/multiple_assignees_for_issues.png)

doc/user/project/issues/sorting_issue_lists.md

@@ -37,7 +37,7 @@ creation date. Issues created most recently are first.
 ## Sorting by due date
 
 When you sort by **Due date**, the issue list changes to sort ascending by the issue
-[due date](issue_data_and_actions.md#due-date). Issues with the earliest due date are first,
+[due date](due_dates.md). Issues with the earliest due date are first,
 and issues without a due date are last.
 
 ## Sorting by label priority

doc/user/project/merge_requests/getting_started.md

@@ -136,10 +136,18 @@ To learn more, read [Review a merge request](reviews/index.md).
 
 ### Merge requests to close issues
 
-If the merge request is being created to resolve an issue, you can
-add a note in the description which sets it to
-[automatically close the issue](../issues/managing_issues.md#closing-issues-automatically)
-when merged.
+To create a merge request to close an issue when it's merged, you can either:
+
+- [Add a note in the MR description](../issues/managing_issues.md#closing-issues-automatically).
+- In the issue, select **Create a merge request**. Then, you can either:
+
+  - Create a new branch and [a draft merge request](../merge_requests/drafts.md)
+    in one action. The branch is named `issuenumber-title` by default, but you can
+    choose any name, and GitLab verifies that it's not already in use. The merge request
+    inherits the milestone and labels of the issue, and is set to automatically
+    close the issue when it is merged.
+  - Create a [new branch](../repository/web_editor.md#create-a-new-branch-from-an-issue)
+    only, with its name starting with the issue number.
 
 If the issue is [confidential](../issues/confidential_issues.md),
 you may want to use a different workflow for

doc/user/todos.md

@@ -29,7 +29,7 @@ Many to-do items are created automatically.
 A to-do item is added to your To-Do List when:
 
 - An issue or merge request is assigned to you.
-- You're [mentioned](project/issues/issue_data_and_actions.md#mentions) in the description or
+- You're [mentioned](discussions/index.md#mentions) in the description or
   comment of an issue, merge request, or epic.
 - You are mentioned in a comment on a commit or design.
 - The CI/CD pipeline for your merge request fails.