GitHub has made issue types and fields generally available for personal repositories, extending structured planning to individual developers and open-source maintainers. Account owners can customize types and fields across their repositories, use the values in Projects and manage them through programming interfaces. Each account can define up to 25 types and 25 fields.
GitHub, the software development and code hosting platform, made issue types and fields generally available in personally owned repositories on 11 November.[1], [2]
Individual developers and open-source maintainers can configure a common planning structure across repositories through their personal account settings. An issue is a work record used to track a bug, task or proposed feature. Types and fields can be set when creating or viewing one.[1]
Default issue types cover bugs, tasks and features, with account owners able to change them or create more, up to 25 types. Default fields include priority, effort, start date and target date. An account can have up to 25 fields supporting text, numbers, dates and single or multiple selections. Fields can be pinned to particular types or made available on issues without a type.[1]
The values can also organize custom views and bulk updates in Projects, GitHub’s planning tool. Programming interfaces allow software to manage types and fields, while event notifications support automated workflows. The same update lets users create labels and milestones directly from an issue when a search finds no match, without opening a separate repository management page.[1]
