GitHub brings issue types and fields to personal accounts
Bug, Task and Feature issue types, plus fields like Priority and Effort, were an organisation-only feature until now. Solo maintainers can use them too.
GitHub has made issue types and issue fields generally available on repositories owned by personal accounts. Both were previously limited to organisations, so a solo maintainer or a side project under a personal username had no way to categorise or triage issues the way a team repo could.
Repositories get three default issue types, Bug, Task and Feature, and four default fields, Priority, Effort, Start date and Target date. You can edit these or add your own, up to 25 issue types and 25 issue fields per account, and manage them from the Issue types and Issue fields pages under Planning in your personal account settings. Fields can be pinned to specific issue types or left available on any issue.
Why it matters: if you maintain an open-source project or a side project solo, you can now get the same triage structure GitHub gives organisations, without creating one just to unlock it. For anyone already using issue types on an org repo, the same fields and types now carry over to personal ones, so there’s no behaviour difference to relearn.