### Resources UX @dimitrieh FE @ClemMakesApps BE @vsizov ### Docs blurb <details> GitLab is a tool that encourages everyone to contribute, and often multiple people likely work on the same issue together. This can especially be difficult to track in large teams where there is shared ownership of an issue, and those multiple folks may not work together day to day. With this release, GitLab enables you to assign as many users as you want to a given issue. Every one of those assignees are first class citizens, and receive the same notifications as before. With this change, you can now also search for issues for two or more assignees. Each search result will have at least the set of assignees you have specified. </details> ### Description * EE Starter Edition * Multiple assignees for an issue * Within an issue, view and edit the multiple assignees. Same existing permissions for these actions as now, for one assignee. * No maximum number of assignees. * The designs should be scalable to 7 assignees. But they don't have to look "good" beyond that. We expect users to use the feature responsibly and not just keep assigning too many people. And so we give the responsibility to them, rather than putting a restriction on the upper limit, since putting an upper limit requires additional work that is not worth it. We don't have upper limits for other fields (labels, participants). So from that perspective, we do not need to enforce an upper limit. * If _there is_ a good reason to enforce an upper limit, that will be a future feature, not in scope here. * When there is an update for an issue, GitLab triggers notification emails and todos for the assignee. For the scope of this issue, the only change is that those triggers happen multiple times for each assignee. That is, each assignee receives the same notification email and todo. Even if the email text copy is worded that implies one assignee, that does not change. That is out of scope for this issue. * Searches in the search bar for issues list is a separate issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/28947 * Update issue export to dump multiple assignees, i.e. updating this https://gitlab.com/gitlab-org/gitlab-ee/issues/1480 ### Out of scope Merge requests are out of scope for this issue. ### Design #### Issue and Issue board sidebar __1 Assignee in the sidebar stay the same__  __2 Assignees an onwards should be 5 Assignees per row in the sidebar__  __6 Assignees and more__  __6 Assignees and more expanded__  ##### Closed sidebar __1 assignee__  __2 Assignees__  __more than 2 assignees__  __more than 99 assignees__  ##### Assigning an assignee from the sidebar  #### Issue board cards Following your "stacked" approach, we can show up to three pictures in the corner | 1 assignee | 2 assignees | 3 assignees | |------------|-------------|-------------| |  |  |  | Through hovering or clicking on the pictures, we can expand them to show a little more detail. We can cover over the issue title with a transparency gradient and slide them out to the left. If there are 4 assignees, we can show them all, and if there are more than 4, we can use the fourth circle to indicate the number of remaining assignees | 3 assignees | More than 4 assignees | |-------------|-----------------------| |  |  | #### Issue list rows __1 to 4 assignees__  __More than 4 assignees__  #### Slash commands __Assigning__  __Unassigning__  #### System note Will follow this pattern, next to what is already there: __assigned to multiple assignees at the same time__  __Assigned to someone if there already is one or multiple assignees__  __removed all assignees__ Show which assignees you unassigned, when you unassigned all assignees. (as this is valuable information). Let's to this up to a max of 5 people.. and let the rest be shown as X others  __removing assignee and assigning assignee__ (same logic as with labels)  __removing assignee and assigning assignee while there still is/are another assignee(s)__  __extra note:__ Unassigned __from__ would be nice as in:  #### Search See: https://gitlab.com/gitlab-org/gitlab-ce/issues/28947 <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->