A small GitHub repository can have a long list of labels and still make it hard to tell what to work on next. A report can be a bug, affect the command-line interface, and need attention before a release. Those are three separate pieces of information. Give each one a clear home and the next triage pass gets easier.
On November 11, GitHub announced general availability of issue types and fields for repositories owned by personal accounts. Start with the default types and one priority field. Try them on a few open issues before changing your entire backlog.
Give types, labels, and fields different jobs
Use the issue type to describe the kind of work. GitHub starts with Bug, Task, and Feature. Keep labels for tags that can overlap, such as cli and documentation. Use a structured field for a value you want to compare across issues, such as priority. If you already have a priority label, choose one place to maintain that decision during the pilot so the two values do not drift apart.
Set up a small pilot in one repository
In personal account settings, look under Planning for Issue types and Issue fields. GitHub lists Priority among the default fields. Before creating another field, check whether the existing one serves your purpose and whether its visibility fits what you plan to record.
Pick a handful of open issues that represent different work. Assign their types, then set priority only where you can explain the decision. In the issue sidebar, use Add field if the field is available to you but absent from the sidebar. The GitHub guide to issue fields explains how to edit or clear a value and how pinned fields appear. Consider pinning Priority only after you know which issue types regularly need it.
Try one triage pass before adding more fields
Imagine a maintainer of a fictional command-line app. They mark a crash on launch as Bug, add the cli label, and set a high priority because the app cannot start. A request for a new export format becomes Feature and keeps the same cli label. It can wait for feedback from users. The label helps find both issues by area. The type and priority tell the maintainer what kind of work each issue needs and what to pick up first.
If your priority options include High, start with a search such as is:open field.priority:high. Check the results against a known issue. An empty result might mean nobody has set the field, or that your account cannot see a restricted value. GitHub documents the field search syntax and visibility rules in its issue fields guide.
Keep the setup easy to maintain
Leave uncertain values blank until someone can make the decision. A guessed target date creates another detail to correct at the next meeting. Before adding a new field, ask what decision it will help you make and who will update it. GitHub currently supports these fields on issues. When work moves to a pull request, link back to the issue and review the change against its original context. TechPulse’s pull request review guide covers the next step.
Prepared with AI assistance using GitHub’s announcement and documentation. The repository example is fictional. Read the TechPulse editorial policy.
✍️ Leave a Comment