Dev News Daily ENDE

GitHub brings issue types and issue fields to personal-account repositories, up to 25 of each

Issue types and issue fields, until now a feature of organisation-owned repositories, are generally available on repositories owned by personal accounts, according to a GitHub changelog entry dated 11 November. GitHub pitches it at individual developers and open-source maintainers who want the same planning structure across their own repositories.

Issue types are managed in the personal account settings, on an Issue types page under Planning. The defaults are Bug, Task and Feature, and an account can customise them and define up to 25 types.

Issue fields sit on a neighbouring settings page. The defaults are Priority, Effort, Start date and Target date. Up to 25 fields can be defined, typed as text, number, date, single-select or multi-select. A field can be pinned to particular issue types or offered on issues that have no type at all.

Both are set when an issue is created or edited, and both work in projects for custom views and bulk updates. For automation, GitHub lists the REST and GraphQL APIs and webhooks as ways to manage types and fields programmatically.

The same entry adds a smaller convenience: labels and milestones can now be created from inside an issue. If a search in the label or milestone picker finds nothing, the interface offers to create it on the spot, without a detour to the repository's labels or milestones pages.

GitHub brings issue types and issue fields to personal-account repositories, up to 25 of each
GitHub brings issue types and issue fields to personal-account repositories, up to 25 of each — Dev News Daily

Why it matters

Maintainers of personal repositories have had to encode type and priority in labels, which carry no structure and cannot hold a date or a number. Typed fields at the account level make the same scheme reusable across every repository the account owns, and queryable through the API.