What the Sub-issue progress field actually does
You have split a big piece of work into sub-issues on GitHub, and now your project board shows a wall of individual items.
You are wondering whether to switch on the “Sub-issue progress” field, or whether it will just add another column nobody reads.
The honest answer: it depends on how you plan to use the view.
This article walks through what the field actually does, when it tends to earn its place, and when a simpler setup serves you better.
GitHub’s documentation describes two related fields you can enable on a project: “Parent issue” and “Sub-issue progress.”
If your organization uses sub-issues, enabling them lets you see the relationships between your issues and the progress made on those issues.
The “Sub-issue progress” field shows how many sub-issues have been completed for each parent item.
So the field is not a percentage gauge or a burndown chart.
It is a count-based view of completion within each parent issue’s sub-issue hierarchy, surfaced directly in your project views.
GitHub documents the setup in its table view: in the rightmost field header, open the menu, look under “Hidden fields,” and click “Sub-issue progress.”
The “Parent issue” field is enabled the same way.
That “hidden fields” detail matters.
The field exists on your project but stays out of sight until you reveal it, so turning it on is a low-commitment change.
If it clutters a view, you can hide it again without touching your issues themselves.
When showing sub-issue progress helps
The field earns its place when your project view is organized around parent work rather than individual tasks.
A few situations where that pattern shows up:
- You group views by parent issue. The “Parent issue” field can be used to group items, letting you create views that break down your work using the sub-issue hierarchies you have created. In a grouped view, a progress count next to each parent gives you a completion snapshot without opening anything.
- You review work at the initiative level. If your team discusses “how far along is this feature?” rather than “is task 47 done?”, a per-parent completion count answers the question people actually ask.
- You filter down to one parent’s work. GitHub documents filtering by the “Parent issue” field to display only items that are sub-issues of a particular issue. You can start by typing “parent-issue” and selecting an issue from the list, or type the full filter using the repository owner, repository name and issue number. In a filtered view like that, progress on the parent is the natural headline.