Multi-select fields for issues and projects — public preview

[sunnyi101]

Multi-select fields are now available in public preview, across both issue fields and Projects. A single field can hold more than one value, like Platform: iOS, Android, Web, and it works the same way on an issue and in a project. Define it once, set multiple values, and filter by any of them.

How it works

• Create a multi-select field at the organization level (issue fields) or directly in a project
• Set one or more values on an issue or project item
• Filter issues and project views by any of those values, for example Platform: iOS OR Android
• Options can have names, descriptions, and colors, just like single select

How to try it

Create a multi-select issue field (organization level)

issue.mp4

1. Go to your organization Settings → Planning → Issue fields (or Issues → Fields).
2. Select New field, give it a name, and choose the Multi-select type.
3. Add your options (e.g. iOS, Android, Web) and save.
4. Open any issue in the org, find the field in the sidebar, and set one or more values.

Create a multi-select field in a project

projects.mp4

1. Open your project and click the + in the table header (or Project settings → Fields → New field).
2. Name the field and choose the Multi-select field type.
3. Add your options and save.
4. Set multiple values on items, then filter by them in any view — for example Platform: iOS OR Android.

Feedback

Share feedback, report issues, or suggest ideas in this discussion.

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.

[ekolis]

This looks useful! It would be really nice, though, if custom fields were available outside of organizations. Is there any cost or maintenance overhead to creating an organization? Or would I be able to create one or more organizations just for the purpose of adding organization-exclusive features to my own repos and standardizing the configuration of the repos? And if I were to do so, would that break existing links to the repos that I migrate to the organizations?