Commit f5f99c90 authored by Sean Packham (GitLab)'s avatar Sean Packham (GitLab)

Merge branch 'docs/issues-multiple-assignees' into 'master'

Add to docs: issues multiple assignees

Closes gitlab-ee#2440 and #32574

See merge request !11556
parents 604c28b2 2696206f
doc/user/project/issues/img/issues_main_view.png

47.5 KB | W: | H:

doc/user/project/issues/img/issues_main_view.png

72 KB | W: | H:

doc/user/project/issues/img/issues_main_view.png
doc/user/project/issues/img/issues_main_view.png
doc/user/project/issues/img/issues_main_view.png
doc/user/project/issues/img/issues_main_view.png
  • 2-up
  • Swipe
  • Onion skin
...@@ -49,6 +49,10 @@ Read through the [documentation on creating issues](create_new_issue.md). ...@@ -49,6 +49,10 @@ Read through the [documentation on creating issues](create_new_issue.md).
Read through the distinct ways to [close issues](closing_issues.md) on GitLab. Read through the distinct ways to [close issues](closing_issues.md) on GitLab.
## Create a merge request from an issue
Learn more about it on the [GitLab Issues Functionalities documentation](issues_functionalities.md#18-new-merge-request).
## Search for an issue ## Search for an issue
Learn how to [find an issue](../../search/index.md) by searching for and filtering them. Learn how to [find an issue](../../search/index.md) by searching for and filtering them.
......
...@@ -6,7 +6,7 @@ Please read through the [GitLab Issue Documentation](index.md) for an overview o ...@@ -6,7 +6,7 @@ Please read through the [GitLab Issue Documentation](index.md) for an overview o
The image bellow illustrates how an issue looks like: The image bellow illustrates how an issue looks like:
![Issue view](img/issues_main_view_numbered.png) ![Issue view](img/issues_main_view_numbered.jpg)
You can find all the information on that issue on one screen. You can find all the information on that issue on one screen.
...@@ -41,6 +41,21 @@ it's reassigned to someone else to take it from there. ...@@ -41,6 +41,21 @@ it's reassigned to someone else to take it from there.
if a user is not member of that project, it can only be if a user is not member of that project, it can only be
assigned to them if they created the issue themselves. assigned to them if they created the issue themselves.
##### 3.1. Multiple Assignees (EES/EEP)
Issue Weights are only available in [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/).
Often multiple people likely work on the same issue together,
which can especially be difficult to track in large teams
where there is shared ownership of an issue.
In GitLab Enterprise Edition, you can also select multiple assignees
to an issue.
> **Note:**
Multiple Assignees was [introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/1904)
in [GitLab Enterprise Edition 9.2](https://about.gitlab.com/2017/05/22/gitlab-9-2-released/#multiple-assignees-for-issues).
#### 4. Milestone #### 4. Milestone
- Select a [milestone](../milestones/index.md) to attribute that issue to. - Select a [milestone](../milestones/index.md) to attribute that issue to.
...@@ -153,14 +168,9 @@ Once you wrote your comment, you can either: ...@@ -153,14 +168,9 @@ Once you wrote your comment, you can either:
- Click "Start discussion": start a thread within that issue's thread to discuss specific points. - Click "Start discussion": start a thread within that issue's thread to discuss specific points.
- Click "Comment and close issue": post your comment and close that issue in one click. - Click "Comment and close issue": post your comment and close that issue in one click.
#### 18. New branch #### 18. New Merge Request
- [New branch](../repository/web_editor.md#create-a-new-branch-from-an-issue):
create a new branch, followed by a new merge request which will automatically close that
issue as soon as that merge request is merged.
#### 19. New merge request
- Create a new merge request (with source branch) in one action. Optionally just create a new branch, as explained above.
![Create new merge request](img/create_new_merge_request.png) - Create a new merge request (with a new source branch named after the issue) in one action.
The merge request will automatically close that issue as soon as merged.
- Optionally, you can just create a [new branch](../repository/web_editor.md#create-a-new-branch-from-an-issue)
named after that issue.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment