We need a way to see Nested Sub-Issues in Project Table View

[Cleve-machine]

Select Topic Area

Product Feedback

Feature Area

Projects

Body

In Github projects you can now add sub-issues. Great.
However if you view issues in a table, there is no way to create a view where you can see a parent issue, with it's sub issues showing in rows directly beneath it.
You can group by parent issue. But then this doesn't work well for filtering and sorting.
We need a way to show nested sub-issues in table view.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[martias]

I would like to upvote this feature. Ir would be great to have the possibility to see sub-issues displaying beneath parent issues in the board.

[yalegria]

Following on this as well.

[PRIYAtechky]

It’s true that GitHub Projects currently supports sub-issues, but the table view doesn’t provide a nested hierarchy display (parent > sub-issues inline). Right now, the closest workaround is:

1. Group by Parent Issue – this clusters sub-issues under their parent, but as you mentioned, it limits flexible filtering/sorting.
2. Use a Board View – the board layout lets you visually organize parent and child issues together, though it’s not the same as a nested table.
3. Custom Fields + Filters – you can add a custom field (like “Parent ID” or “Epic Link”) and filter/sort that way to mimic hierarchy.
4. Third-party tools (e.g., ZenHub, Linear, or Jira integrations) – these support true nested issue hierarchies in table-like views.

[programma256]

I would also like to upvote this. I was previously using ADO and found a nested hierarchy view very helpful to browse and organise/prioritise the whole product backlog, update task iterations, etc. Not having this is quite a hinderance actually - I can't see an easy way to visualise the whole backlog for the team.

Coming from ADO it's a bit confusing why group by parent issue doesn't automatically work recursively. The current functionality presents all the same information but scatters the task relationships into 2-level chunks which is frustrating to work with. This would also align the functionality across sub-issues and projects - currently I'm forced to explore the sub-issues tree when I actually want to be working in the board.

Furthermore whilst you can sort manually, when grouping by parent you can't change the sort order for the parent and you can only change the sort order of the sub-issue within the parent. My first instinct was to use the manual sort to drag-and-drop the issues/parent issues into a more intuitive order but due to the above this isn't possible.

The best I've come up with so far in terms of workarounds is that I can position all my Epics and their top-level Features at the top by prefixing '[EPIC] ' to the Epic title.

[MakePixelsWork]

I raised this issue before, but its topic got auto-closed by the bot. Would love this nesting feature in the main view of the table.
Closed request: https://github.com/orgs/community/discussions/156950

My work-around currently is to add the Agile work-items on your Company profile, which you then can apply to all your Projects, and sort accordingly. You'll however still have to click the topmost work-item (in our case, the Epic) and then view the sub-issues overview that GitHub Projects already provides.

Maybe they think this clutters the main table view... but I for one would love to have this nesting feature in the main view.

[hdm12345]

Upvoting this!! It's really hard to visualize sub-issues in the main view.

[jmjech]

I also upvote this feature! A nested parent-child-child-... would improve readability considerably.

[drewclifton]

Yes, we need to be able to "group by" something (I am using a custom field for this), and also see nested issues (grouping by and nesting issues are two different concepts). Thanks so much for receiving this feedback!

[RichardKong-Ola]

They just added the View Hierachy option to Private Preview build which should fulfill the requirements raised, although I can't tell if it can show multiple levels of sub issues.

[programma256]

Thanks for the heads up! Looks like this has been addressed :) https://github.com/orgs/community/discussions/180425

[ricardo-cunha-wmx]

Maybe I'm not configuring it well, but my sub-tasks appear both inside and parallel to the parent: https://github.com/user-attachments/assets/22cb5158-a55b-4cba-a0f8-9e2bd9eb711c (you can see 4, 5 and 6 repeats under GRILLE 9)

Also, it'd be great if sub-task cards would be slighty placed to the right under the parent to indicate dependance in the Kanban view, but obviously they could be in different stages, so maybe this isn't as obvious as I think

https://github.com/user-attachments/assets/fb9997bc-a48a-49f4-9657-2fc910658298