Allow group by with "root parent issue"

[8ma10s]

Select Topic Area

Product Feedback

Feature Area

Projects

Body

Feature I'd like to see

I would like GHP to allow grouping of the issues either by their root parent issues (the topmost issue within the nested parent-child structure).

Background

Our team organizes the issues within GHP with the nested structure like the following:

• Projects: these issues have type: Project.
• Epics: these issues have type: Epic. Each epic is a child of one Project.
• Issues: just regular issue (no type). Each issue is a child of one Epic.

(I know some may say "we should have a single GHP project per project, but since our team has a lot of short-term, small projects, we see it more convenient to take this approach to avoid having to create a new GHP project every single time)

Basically, I would like to create a view for issues and categorize them based on which Project they belong to.

Current situation

With the current feature, it allows us to only group the issues by the Epic they belong to (or basically, group by parent issue). However, this is a bit inconvenient as we have multiple epics per project, and sometimes the "group by" list gets too long, when all we want to do is "just take a look at what issues we're currently working on for a particular project".

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. ⭐