Support multiple assignees for Projects

[WilberRojas]

Actions before raising this issue

• I searched the existing issues and did not find anything similar.
• I read/searched the docs

Is your feature request related to a problem? Please describe.

Hello,

I’ve been trying to assign a large 'Project' to more than one user, so that it can be supervised by 2 or 3 people at the same time. However, when assigning responsibility, the interface only allows selecting a single user.

Creating a separate 'Organization' for each 'Project' that requires multiple supervisors doesn’t seem like a suitable or scalable solution. I’ve reviewed the official documentation and existing issues, but couldn’t find a way to achieve this or a similar request.

(I’d really appreciate any guidance, if there is currently a way to implement this kind of multi-user assign)

Describe the solution you'd like

What I’m proposing is to allow assigning multiple users by using commas or another separator when specifying assignees. I’ve attached an image to illustrate the idea:

Describe alternatives you've considered

Another option, although more elaborate, would be to make it work similarly to labels, displaying a small tag or box for each assigned user.

Additional context

No response

[TatshSiow]

Hi, I was working on this on a custom tailored version, unforntunately I can't share the source code
I did try your version UI approach before, but it will be problematic if the assigned user list grows larger (e.g. 5 or more users, the name will exceed the viewable area (UI) )

My approach is :

• leave assignee alone
• add assignees function
• if assigned user more than 1, goes into assignees list

So, you won't have to deal with the conflict of the original assignee function

Here is a sample of the image

[Sayamgarg1]

Thanks for sharing this approach, it makes a lot of sense
Keeping the original assignee field and introducing a new assignees list
will avoid backward compatibility issues.

I’m happy to implement this solution:

• Preserve current single assignee behavior
• Add multi-assignee support using a separate field
• Update backend + UI accordingly

Before I start

1. Should both fields coexist permanently?
2. Preferred UI: multi-select dropdown (like your example)?
3. Any API design constraints I should follow?

Looking forward to your guidance

[TatshSiow]

1. both assignee and assignees share the same field, if

• only 1 assignee : put it into the assignee list
• 2 or more assignees : put it into the assignees list

2. multi-select dropdown is recommended since it will grow too long if there are a bunch of assignees
3. For what i change, i only make a case decision of assignee and assignees, depends on the total selected assignees, then take action based on the count (I'm not sure what approach will be better, but this is what I made)