Playbooks · Everyday tasks
GitHub issue types reach personal repos
Written November 12, 2026
Solo maintainers get the planning structure that used to require an organization: define issue types and fields once in account settings, and they apply across every repository the account owns. It takes one sitting to set up.
What changed
Issue types and issue fields are now generally available on repositories owned by personal accounts, in GitHub's changelog entry dated November 11, 2026. Until now this was an organization feature. A solo maintainer had labels and milestones, and nothing structured beyond them. Now the same planning capabilities are available to individual developers and open source maintainers, defined once and applied across every repository the account owns.
Set up your issue types
Open your personal account settings and go to the Issue types page under Planning. GitHub provides three defaults: Bug, Task and Feature. Adjust those first — rename them, recolour them, or drop the ones you will not use — before adding your own. You can create up to 25 issue types in total. Keep the list short: a type only helps if the person filing the issue can pick the right one at a glance.
Set up your issue fields
On the Issue fields page, also under Planning in account settings, GitHub provides four defaults: Priority, Effort, Start date and Target date. You can create up to 25 issue fields. Fields can hold text, a number, a date, a single choice from a list, or several choices. You can pin a field to a specific issue type, so Effort appears on features but not on bugs, or make a field available on issues that have no type at all.
Two of the defaults do most of the work for a small project. Priority turns a flat issue list into an order. Target date turns good intentions into a visible miss when a date passes. Add more fields only when you find yourself writing the same information into issue bodies by hand.
Use them day to day
Set the type and the field values when you create an issue, or open an existing issue and set them there. Because the definitions live at account level, the same types and fields are ready in every repository you own — there is no per-repository setup to repeat. In GitHub Projects, types and fields can drive custom views and bulk updates, so a board can group work by type or sort it by priority without a separate project-only field to keep in sync.
The same release adds a smaller convenience: you can now create a label or a milestone directly from an issue. If a search in the label or milestone picker finds no match, GitHub prompts you to create one on the spot instead of sending you to the repository's labels or milestones pages.
Automate it, if you outgrow the settings pages
Issue types and fields can be managed programmatically through the REST and GraphQL APIs and webhooks. For a solo maintainer that is mostly future insurance: the settings pages cover the setup, and the API route matters when a script creates or sorts issues for you.
Limits
- The caps are 25 issue types and 25 issue fields per account. That is plenty for one maintainer and a real constraint for anyone trying to model a large taxonomy.
- Definitions are account-wide. One set of types and fields serves every repository you own, so two projects with very different workflows share the same structure.
- The changelog describes fields on issues and in Projects views. It does not describe field values being set from issue templates, so keep collecting anything a template must capture in the template itself.
Related playbooks
- Nod: n8n's open-source personal agent
- Set up Nod, n8n's personal agent
- Claude reads your bank statements now — in the US
- AlphaGenome 2 reads variants per cell type
Sources
Back to: Everyday playbooks hub · Also: Dependabot pauses alerts on quiet repos · Patch your MCP reference servers now