Multiple assignees on Issues and Pull requests

Surprised to see so much negative feedback. I agree that clear responsibility is important, and that adding multiple assignees when those people share similar responsibilities could lead to the bystander effect.<p>I&#x27;m really excited about this feature. I feel like &quot;If only GitHub Issues allowed multiple assignees&quot; comes up in conversations with colleagues at least a couple times a month.<p>For context, the design (and development) team I work with uses GitHub Issues religiously. Right now all issues that need design work are explicitly assigned to a designer, and we use a label based workflow combined with Codetree to help organize weekly sprints. Having multiple assignees will allow us to explicitly assign a product manager to each of these issues w&#x2F;o having to take it out of each designer&#x27;s sprint, which will help make sure all design tasks receive feedback and move forward in a timely manner.

The best way to make sure something never gets done is to share ownership of it.

Wasn&#x27;t expecting such a negative reaction to this. For Issues, the feature isn&#x27;t particularly useful to me, but for Pull Requests, it&#x27;s a great way of declaring who needs to sign off for the PR to be merged. When big features come into PR, people where I work were reluctant to use the &#x27;Assignee&#x27; feature at all because it implied that the PR was already &#x27;taken&#x27; for code review. Now, a front end engineer can assign themselves to do the FE review and a back end engineer can assign themselves to do the BE review, and the reviewers can be directly seen from the PR list. Nice.

Does anyone know if it&#x27;s possible to disable this? For teams like mine, where we want to have only one owner for each issue, it&#x27;s meant many more clicks to perform a reassignment operation.

There are many improvements needed on Issues; this one is certainly not the first that comes to mind.

Great! Now it would be cool if I could save a group so I could in one click assign my pr&#x27;s to my team instead of having to individually add each member each time

Assigning pull requests to multiple people is fantastic: sometimes you&#x27;re modifying a library and want the owner of that library to review your code, but you&#x27;re simultaneously modifying the clients of that library and want their owners to review the change as well.<p>Assigning issues to multiple owners is a recipe for complete and utter inaction from all parties involved.

This is bad practice for getting things done.

I&#x27;m glad this feature is in, but it&#x27;s only useful for my PRs.<p>For example, there was a recent PR where the owner was modeling the UI for a feature with stubbed calls, while I was setting up the backend.<p>Once my work was done, he wrapped up the rest, and I was no longer needed.<p>We used notifications to informally say &quot;you&#x27;re still needed for this!&quot; vs it being part of my daily hit list.