The Butler
Back to briefings
GitHub / Personal projects

GitHub's new personal-account issue fields can make a side project easier to restart

· The Butler · 4 minute read

The metallic robot Butler in formal attire in a warm lounge setting.
Butler editorial illustration, not a product screenshot.

A neglected side project rarely needs a bigger dashboard. It needs a clear answer to a smaller question: what was I doing, and what should I do next?

GitHub's November 11 update makes issue types and issue fields generally available for repositories owned by personal accounts. The defaults include familiar types such as Bug, Task and Feature, plus fields such as Priority and Effort. You no longer need an organization-owned repository to use this particular structure. GitHub's announcement.

That is a meaningful extension of the planning tools we covered in our earlier issue-fields briefing. The interesting opportunity now is less enterprise process and more a manageable notebook for the person building something between other responsibilities.

Start with three decisions

For a small app, our suggested first pass is simple. Give each issue a type, decide whether it matters now or later, and write a sentence describing what finished looks like. Use the issue body for that final sentence; you do not need a custom field for every thought.

Consider an export bug. A title such as Fix saving leaves next weekend's version of you doing detective work. An issue titled Export with three images fails to reopen gives you a starting point. Its completion sentence might say: a project containing three images exports, imports into a fresh session and retains all three images. That is an illustrative test, not a report about a particular product.

A new feature can use the same pattern. Add search becomes Find a character by name from the project overview. The type helps you sort the work; the sentence helps you do it.

Keep one place for priority

GitHub distinguishes issue fields, which belong to the account or organization and follow issues across repositories, from project fields scoped to an individual project. The two can coexist. If you already track Priority in a project, adding another Priority field without deciding which one wins can make the board less clear rather than more organized. GitHub's field documentation.

Our recommendation is to try the new arrangement on a handful of open issues before converting an entire backlog. Ask whether you can identify the next useful task in thirty seconds. If not, another dropdown is unlikely to solve the problem.

GitHub supports account-level management of issue types, including disabling types rather than deleting them. That gives you room to simplify a classification system that turned out to be too ambitious. Managing issue types.

A better handoff to yourself, or an AI assistant

A clearly written issue is useful whether a person or a coding assistant picks it up. It can describe the observed behavior, the expected result and a small test. Structured fields help group that work, but they do not replace the explanation.

For AI-assisted work, add one boundary in ordinary language: which part of the app should change, and which working behavior should remain untouched. A task about export reliability should not turn into a surprise redesign of the editor. That is a workflow recommendation, not a promise that GitHub's new fields enforce those boundaries automatically.

Check field visibility before putting internal notes into a public repository. GitHub documents public and restricted field visibility, with different access implications. Do not treat a convenient planning box as private merely because you created it in your own account. Field visibility guidance.

The best version of this update may look unimpressive: fewer vague tickets, one trustworthy priority and enough context to resume after a long week. For a side project, that can be more valuable than a perfectly decorated board.