Issue fields: the 100-option limit caps an organization at 100 components #213202
Unanswered
sakaal
asked this question in
Projects and Issues
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Issues
Body
Feature request: raise or scale the option limit of organization issue fields
A Component field is one of the most common issue attributes in software work: Jira, Bugzilla and Trac all have one, and teams migrating to GitHub expect it. With issue fields it naturally belongs at the organization level, so that every repository and project shares one vocabulary and cross-repo views can filter and group by it.
But the limit of 100 options per select field then caps the whole organization at 100 components. For any software house with more than a handful of repositories, that is low: one module per repository, plus a few shared areas (CI/CD pipelines, agent configuration, infrastructure), reaches it quickly. Defining a field per repository is not a way out, because field names are unique per organization, fields cannot be scoped to repositories, and the organization has only 25 fields.
Any of these would solve it:
Please also document the option limit for multi-select fields; the current limits table states only the single-select limit.
Related: #189141 (issue fields general availability), #175366 (repository-scoped issue fields were asked for during the private preview).
Guidelines
All reactions