diff options
Diffstat (limited to 'doc/user/project/issues/multiple_assignees_for_issues.md')
| -rw-r--r-- | doc/user/project/issues/multiple_assignees_for_issues.md | 35 |
1 files changed, 9 insertions, 26 deletions
diff --git a/doc/user/project/issues/multiple_assignees_for_issues.md b/doc/user/project/issues/multiple_assignees_for_issues.md index 105dcd529c8..db160b6cfe8 100644 --- a/doc/user/project/issues/multiple_assignees_for_issues.md +++ b/doc/user/project/issues/multiple_assignees_for_issues.md @@ -4,39 +4,22 @@ 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 --- -# Multiple Assignees for Issues **(PREMIUM)** +# Multiple assignees for issues **(PREMIUM)** -> Moved to GitLab Premium in 13.9. +> Moved from Starter to Premium in GitLab 13.9. -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 large teams with shared ownership, it can be difficult +to track who is working on an issue, who's already done, or who hasn't started yet. -You can also select multiple [assignees](managing_issues.md#assignee) for an issue, making it easier to +You can add multiple [assignees](managing_issues.md#assignee) to an issue, making it easier to track, and making clearer who is accountable for it. - - -## Use cases - -Consider a team formed by frontend developers, backend developers, -UX designers, QA testers, and a product manager working together to bring an idea to -market. - -Multiple Assignees for Issues makes collaboration smoother, +Multiple assignees for issues makes collaboration smoother, and allows shared responsibilities to be clearly displayed. All assignees are shown across your team's workflows and receive notifications (as they would as single assignees), simplifying communication and ownership. -Once an assignee had their work completed, they would remove themselves as assignees, making -it clear that their role is complete. +After an assignee completes their work, they remove themselves as an assignee, making +it clear that their task is complete. -## How it works - -From an opened issue, expand the right sidebar, locate the assignees entry, -and select **Edit**. From the dropdown menu, select as many users as you want -to assign the issue to. - - - -To remove an assignee, clear them from the same dropdown menu. + |