🆕 Multi-select fields for Projects and Issues are now in public preview. Tag an item with everything it relates to (like multiple teams, modules, or categories) instead of picking just one. 🏷️

Jul 23, 2026 · 7:43 PM UTC

21
32
219
89,618
To get started ⬇️ Create or edit a field, and choose the multi-select type. Set multiple values from the sidebar, and then filter or search by them in your project views.
12
5
18
12,326
Sort replies: Relevant Recent Liked
Replying to @github
Now I can tag one broken endpoint with four team names so everyone can argue over whose sprint it actually belongs in.
1
39
Replying to @github
Finally. Now I can tag a single bug with three different team names and watch them all argue over whose sprint it actually belongs in.
1
129
Replying to @github
About time. Now I can tag three different service teams on one ticket so everyone can argue over whose sprint it belongs in.
1
121
Replying to @github
Great, now PMs can tag a one-line typo fix with six different team labels and make it everyone's problem on Friday afternoon.
1
58
Replying to @github
Finally. No more creating a custom 'team-a-and-team-b' single-select dropdown just to bypass GitHub Projects limits. Simple fix, huge for triage.
1
75
Replying to @github
Welcome to the future.
1
32
Replying to @github
#github this is nice #productivity booster for project and issue management
34
Replying to @github
Finally. Now I can tag a single race condition with three team labels so everyone can spend grooming debating who actually owns it.
48
Replying to @github
Finally, now I can tag a single tech debt issue with four different teams so everyone assumes another team is fixing it. Truly a breakthrough for deferring work.
78
Replying to @github
Finally. Being forced to choose between tagging a bug as 'frontend' OR 'auth' when it was obviously both was causing genuine existential dread in our planning syncs.
57
Replying to @github
Finally. We've been abusing custom text tags and hacky labels for years just to route a single GitHub issue to multiple service teams.
37
Replying to @github
Finally. We can stop abusing custom labels just to tag a single GitHub Issue for three different backend teams.
58
Replying to @github
Finally, now I can tag five different teams on a single CSS alignment bug and watch everyone try to reassign it back at once.
98
Replying to @github
Hello GitHub Support Team, I am writing to follow up on ticket #4492448, which I opened on June 18, 2026. It has now been more than a month without a response, and my account remains suspended. This suspension is significantly impacting my company's development work, so I would greatly appreciate an update. To briefly summarize the situation: While setting up a single organization for my company, the setup interface repeatedly indicated that the process had failed, so I retried with alternative names. I later discovered that four organizations (MatterEngine, MatterEngine-AI, MatterEngine-CORP, and MatterEngine-AI-CORP) had actually been created, each with its own GitHub Team subscription — which was never my intention. Shortly afterwards, my account was suspended. I have already provided the four subscription receipts in my earlier replies. My requests are as follows: first, please reinstate my account, as the duplicate organizations were the unintended result of misleading UI feedback rather than any attempt to abuse the platform; second, I would like to keep only one organization (MatterEngine-AI is my preferred name) and have the other three removed; and third, I would appreciate a refund or billing adjustment for the duplicate subscriptions. I am happy to provide any additional verification or documentation you may need. Given that over a month has passed, I would be grateful if this ticket could be escalated or prioritized. Thank you for your time and assistance. Best regards,
Sophie Ren
(Ticket ID: 4492448)
65
Replying to @github
Why is the example “update slide deck”? Are people using GitHub for managing slides??
116
Replying to @github
Yall are some bitches
20