[Projects Beta] Support "Multi select" field

[creasty]

In my company, for instance, we often create issues that span different areas of development (i.e. design, frontend, backend, etc), and we would like to manage this attribute as a multi-select field.
Ideally, those issues can be divided into smaller subordinate issues for each area, but we tend to do so as we go.

This could also benefit the scenario where users want to manage issues that concern multiple teams.

[edmundmaruhn]

I'm currently working on a larger application and we divide it into broader components. To reflect these components we use a single-select, but several times issues arise which are related to multiple components at the same time.

A multi-select would better reflect this instead of insanely adding multiple single-selects or circumvent the absence of a multi-select by messing up issue labels which would have to be duplicated into multiple repositories.

[Julian-Dumitrascu]

We don't need to explain this to developer 1 when developer 2 is offering this feature. Developer 1 should just include it themselves.

[amadeogallardo]

Multiselect would be great for us since we track which customer(s) requested/reported an issue.

[harsh04]

Multi-select is a much-needed field for managing projects right now. Similar to assignee

[ccolella-mdc]

Multi-select custom fields would be an invaluable feature!

[alexcombessie]

We need multi-select to track with customers asked which features. This is not possible without multi-select.
Unfortunately, we cannot use Github projects without this.

[umassahu]

Yes its much required , kindly implement the same so that we can run multiple test suites

[ntindle]

Would love this feature as well

[nikkko]

Requesting this as well. Critical to track which customers have requested for a feature. Should work like labels, but based on a different list.

[alexcombessie]

💯 I cannot believe that Projects was released in General Availability without this feature. Not being able to add multiple tags is a major blocker.

[jaclynjessup]

Currently having to create a mashup of emojis when picking a type for the issues within our board. Multi-Select would significantly cut down on the amount of emoji mashup options I have to create

[av365app]

Currently having to create a mashup of emojis when picking a type for the issues within our board. Multi-Select would significantly cut down on the amount of emoji mashup options I have to create

That's sounds good.

[kiview]

That's a really cool workaround, thanks for sharing 👍

[kathy-phet]

We really need multi-select! And have been waiting almost a year. Can it make it on the project board?? Doesn't seem too hard. You already have the "Assignee" acting like a multi-select. Generallize that behavior and your set.

[kathy-phet]

This issue seems buried - but important ... it's one of your TOP requests for projects by up-votes, that hasn't been addressed.
https://github.com/community/community/discussions?discussions_q=label%3AIssues+sort%3Atop

Can someone please add the appropriate tags "Projects", "Enhancement"? My team really needs this feature.

[ruanyl]

I understand that "issue" could have multi-labels, but this multi-select custom field is crucial for tasks that are not issue-ready.

Perhaps there are performance/product concerns of supporting custom multi-select fields, but please do response to the community request as there are so many people voting and waiting for this feature 🙏 🙏 🙏

[d3rp3tt3]

I work with both private and public repos - these are pulled into one project. We can't use labels to track private stuff on public issues. It is really broken.

[kathy-phet]

@azenMatt - Tagging you in hopes that you might take a look at this request for a multi-select field on project boards. It is one of our top two requests for the project boards to be more useful - and it seems like the request is buried by newer requests - despite the large number of up-votes it has. Thanks for taking a look! And please add appropriate new labels.

[Jay-o-Way]

In contrast to all the "me too, me too" comments, it would be helpful to have specific use-case examples

[nikkko]

Plenty of use cases in the comments above.

[justyn]

There have been a few examples already in the earlier comments about the need for multi-select, but here are two of ours.

🤞🤞 for this to be discussed and added to the roadmap in some form.

Identifying affected products

A product can consist of multiple repositories for various hardware and software elements, and some of these repos may be used by multiple products.

Currently there is no way in Projects to categorise which products are affected by a task/issue. Single-select is not suitable because an item can (and often does) affect multiple products.

Identifying relevant teams

Similarly, an issue may (and again often does) affect multiple teams.

[mich-a-b]

In our project that we are developing, we need to indicate which modules are being affected by these bugs, and having a multi-select feature will be greatly beneficial when working with these use cases.

[heather-ashmore]

Also supporting the need for this multi-select field!

[gilmorera]

+1

[rubengalle]

Any updates to this feature request? It would be useful to be able to add multiple stakeholders to an issue so that they can be kept in the loop during or after development.

[GuillaumeFalourd]

+1 😄

[zsloane]

I guess we're not getting this basic functionality at this point. It's approaching 3 years with no meaningful update.

All focus clearly shifted to Copilot...

[icexuick]

Oh, man this really is needed it almost any type of application/flow.
Does anybody know if there is a official wish-list/forum where to go to regarding this?

[nikkko]

Can we get some sort of update here? Or is it easier to just switch to JIRA?

[vaz3r]

Multi-select is an integral part of the "projects" product and it must be prioritized, I still do not understand why it wasn't to date.

[jerradneff]

+1 on this.

[devison]

This is a feature we quickly realized we need as we are started working with GitHub Projects.
Is it on a roadmap?

[dallenbaldwin]

+1 for my team. A couple of us are piloting GitHub Projects for an upcoming Milestone (the team uses ClickUp currently) and we quickly realized you can only add a multi-select like field once an issue has been created, and it has to be labels. This might be ok for some workflows, but we'd love a multi-select

[dgiacomo]

Can you get Github Copilot to implement this for us please?

[mikahpinegar]

My team desperately needs this feature. We are using GitHub projects for cross team planning and lots of issues get assigned to multiple teams. Only having a single select is a major frustration.

[NCatalani]

In hindsight this thread is ridiculous. Are there any more possible excuses from a technical standpoint for not having this 3 years later down the line?

[azenMatt]

I can assure you all this is still on the radar and I am painfully aware that this new field request (along with the adding of date fields like created / closed) is overdue. Right now we are blocked from working on this until we complete https://github.com/orgs/community/discussions/139936. Once the re-platforming there is finished we will pick these back up