[Projects Beta] Support "Multi select" field

[creasty]

Important

Read the latest update from a GitHub staff:
https://github.com/orgs/community/discussions/6580#discussioncomment-4887894

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.

[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

[nicodard]

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

[nicodard]

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.

[amenity]

@azenMatt - any chance there's been progress since 10/25? 😬 🙏🏻

[triclambert]

Piling on... this should be an obvious win with your customers. Any chance you'll prioritize this any time soon? 🙏

[Arctiq-Ueb]

Obvious bump... Let's make it happen!

[JehlickaJo]

+1

[ezatti]

+1

[sebaaaz]

Any updates on this? Thanks!

[JulianNymark]

multi-select would be nice :) please add it!

[amenity]

@labudis @broccolinisoup - I realize that this highly sought-after request applies to custom project fields, not issue fields. Should I open a new thread to get it in the issue fields backlog?

[labudis]

We are planning to introduce this feature across both Issue fields and Project fields at the same time - work is underway!

[GregJohnStewart]

So I now see the multi select field as an option, but there is no ui for actually adding options? Nothing changes when I select MultiSelect (like with single select). Thoughts? Is it just me?

[labudis]

Hey folks, we are actively working on the multi-select feature to bring it to both Issue and Project fields. This control accidentally "escaped" before it was ready and I am very sorry for the confusion. It's not long now!

[amenity]

I hate to ask the dreaded question, but can you estimate a release date for this, @labudis? Basically just wondering whether we're looking at weeks or months. 🙈

[amenity]

@aconsuegra & @broccolinisoup - any word on multi-select?

[aconsuegra]

@amenity We are testing it internally now, and hope to have it ready in production in a couple of weeks

[amenity]

Excellent! Thanks for the quick reply, @aconsuegra

& Lmk if you need a pre-release tester. I can write some solid bug reports. ;)

[Lindbergo]

Hey! Does anyone know where this is upto? This would really improve the use of projects for us :)

[sahanakothandapani1]

Multi-select fields would also be helpful for educational and student projects. While exploring open source, I've come across issues that fit into multiple categories at the same time, such as documentation, frontend, and testing. Having a multi-select field would make organizing these issues much simpler than creating multiple separate fields or relying solely on labels.

[sunnyi101]

This is live now - https://github.blog/changelog/2026-07-23-multi-select-fields-for-projects-and-issues-in-public-preview/!

[ayy-bc]

@aikenka we just shipped GQL support for multi select so that should be live now :)

And copy pasting is currently being fixed so we should have support for that shortly (by end of day) as well

[aikenka]

Excellent on both counts - thanks @ayy-bc! I've tried the copy/paste successfully, and Claude is happily GraphQL'ing away at updating all the other issues on my board.

Will we be able to "group by" these fields as well?

[ayy-bc]

@vb-dontenwill this (not able to clear options from issue page) should be fixed now 😄 thank you so much for being early users and reporting the bugs 🙏

[aikenka]

Will we be able to "Slice by" these fields as well?

[amenity]

@ayy-bc - +1 to @aikenka's question - I love "Slice by" and "Group by" for the GHP table view. I realize it's a bit illogical to have this work for a multi-select field because things will show up twice, so the number of rows will not match the number of distinct issues... but I think I'd still like the option to navigate issues in that way.

[amenity]

Working beautifully so far. Thanks!

[grendes-wunder]

I try to use such a Field on Organization level, as Issue field.
I have configured a Project Boards' view to display this new field ("Component") on the Issue's card but no luck.
Most other fields do show up. What do I miss? Could this be a bug / not supported on Issue cards?

[Arctiq-Ueb]

For anyone using GraphQL to call multi-select fields, you should refer to 'ProjectV2MultiSelectField'.

example

gh api graphql -f query='
{
  node(id: "#{...}") {
    ... on ProjectV2 {
      fields(first: 50) {
        nodes {
          ... on ProjectV2MultiSelectField {
            id
            name
            multiSelectOptions {
              id
              name
            }
          }
        }
      }
    }
  }
}
'