On 11 November 2026 GitHub announced that issue types and issue fields are now generally available on repositories owned by personal accounts. Until now these planning features were an organisation-level tool.
What GitHub says
- Issue types. Defaults are Bug, Task and Feature. You can customise them and create up to 25.
- Issue fields. Defaults are Priority, Effort, Start date and Target date. You can create up to 25, as text, number, date, single-select or multi-select fields, and pin them to specific issue types.
- Where to set them. In personal account settings, under “Planning”.
- Who it is for. GitHub frames it as bringing the same planning capabilities to individual developers and open-source maintainers.
Why a non-developer should care
Many early-stage products start in a freelancer’s or founder’s personal GitHub account. Until now, the work tracked there was a flat list of issues with free-text labels. With typed issues and structured priority and effort fields, you can ask for a status view that does not depend on someone’s memory: how many bugs, how big, what is due.
It also gives AI coding agents better-structured work to pick up, because a well-typed issue with an effort estimate is a clearer brief than a one-line title.
So what
If your product’s repository sits in a personal account, ask your developer to switch these fields on and report from them. If it should live in an organisation account instead, that is a governance conversation worth having early. Our AI-assisted development service sets up delivery tracking like this from day one. To talk it through, start a project.