GitHub announced on November 11, 2026 general availability of issue types and issue fields for repositories that belong to personal accounts. Until now, these planning tools were tied to organizations, so solo developers and maintainers who keep projects under their own username had to rely on labels and free-text conventions instead.
The same update also lets anyone create a new label or milestone straight from an issue. For individual maintainers who run several repositories, the change means bugs, tasks and feature requests can be classified the same way everywhere, with structured data such as priority and target dates attached directly to each issue.
What GitHub Changed
Issue types and issue fields first arrived as organization-level features. With this release, the owner of a personal account can define them once in account settings, and they then apply across every repository that account owns. GitHub frames the move as giving individual developers and open source maintainers the planning structure that teams inside organizations already had.
The changelog lists four practical parts of the rollout:
- Custom issue types: set up from the Issue types settings page in the Planning area of personal account settings, with Bug, Task and Feature provided as defaults and room for up to 25 types.
- Custom issue fields: configured on the Issue fields settings page in the Planning area, starting with four defaults: Priority, Effort, a start date and a target date, again up to 25 fields.
- Use on issues and projects: type and field values can be set when an issue is opened or later, and they can drive custom views and bulk edits in GitHub Projects.
- Automation: the REST API, the GraphQL API and webhooks can read and manage types and fields.
Key Details on Types and Fields
An issue type is a single classification per issue, and it appears in issue lists and on the issue page itself. GitHub's documentation explains that types can be renamed, recolored, given a description, disabled or deleted. A disabled type is hidden but comes back on older issues if it is enabled again, while a deleted type is gone for good.
Issue fields hold structured metadata. According to the announcement, fields can hold free text, numbers, dates, or one or several choices from a list. The default Priority field offers Urgent, High, Medium and Low, and the default Effort field offers High, Medium and Low, but all of these can be renamed, reordered or removed.
Fields can be pinned to specific issue types, so a bug shows only the fields that make sense for bugs. The docs suggest pairing a Severity field with bugs and an Impact field with features. A field can also be pinned to untyped issues, and up to 10 fields can be pinned per type.
Visibility and Limits
For public repositories, each field has a visibility setting. Restricted, which is the default, limits the field to you and to collaborators who can at least read the repository, while Public shows it to anyone viewing the issue. GitHub says this setting is applied consistently in the web interface, the API, timeline events and search suggestions.
There are a few limits worth knowing before you design a scheme:
- 25 issue fields and 25 issue types per account.
- 100 options in a single-select field.
- 50 fields in total per project, with issue fields and system fields counting toward that number.
- Only Public fields can be used in public projects; switching a field to Restricted removes it from such projects.
Labels and Milestones From the Issue Page
The second change is smaller but saves clicks. When you search for a label or milestone on an issue and nothing matches, GitHub now offers to create it on the spot. Previously you had to leave the issue, open the repository's labels or milestones page, add the item and come back.
What It Means for Developers
Many solo maintainers have used labels such as "bug", "p1" or "needs-estimate" to fake structured data. That works, but labels are free-form and differ from one repository to the next. Account-wide issue types and fields give you one shared vocabulary, so filtering all your bugs or all urgent work across repositories becomes straightforward.
Because each value is stored on the issue, fields also beat project-level custom fields. The same priority follows an issue into every project that includes it. If you already track priority in a project field, migrate gradually to avoid two competing Priority columns.
For automation, the API and webhook support means triage bots, release scripts or GitHub Actions workflows can set a type or priority as issues arrive. Keep the default Restricted visibility for internal signals such as effort estimates, and make only the fields that help contributors public.
How to Get Started
Open your personal account settings, go to the Planning section and choose Issue types or Issue fields. Review the defaults, rename or remove what you do not need, then pin each field to the types where it should appear. After that, open any issue in a repository you own and set its type and field values from the sidebar.
If you maintain automation around your repositories, our coverage of GitHub Actions workflow lockfiles and ACCESSIBILITY.md statements on repository pages shows other recent GitHub changes aimed at maintainers.
Conclusion
Personal accounts can now use issue types and issue fields, not only organizations, and creating labels or milestones no longer requires leaving the issue. For individual developers and open source maintainers, it is a simple way to replace ad hoc labels with consistent, filterable planning data across all of their repositories.
Sources
- GitHub Changelog: Issue types and fields are available for personal accounts
- GitHub Docs: Managing issue types
- GitHub Docs: Managing issue fields
See my articles more often when you search Google.
