Nested Projects or Portfolio View

[webdog]

It'd be great if GitHub Projects had either the capability to create Projects underneath Projects, or a Portfolio view in which many projects could be grouped together.

For example, I could have an overall project that is tracking many large inter-related deliverables. Each deliverable could be a project unto itself, and would benefit from the granularity of separating the concerns from an upstream project to a downstream project (Or vice versa).

[darknet-ghost]

I'd like to see this capability as well, particularly for managing complex software development with multiple related workstreams and different project lifecycles.

One use case is an application or framework that remains under active development for years. The primary GitHub Project serves as the central location for the product backlog, roadmap, ongoing development, and overall reporting. That Project might remain open for the entire lifetime of the application.

However, there are also finite activities associated with that same product that would benefit from their own Projects.

For example, each software release might require a dedicated manual QA effort. A GitHub Actions workflow could create a new QA Project from a template, populate it with release-specific test execution issues, and track validation through completion. Once the release passes QA, that Project can be closed while retaining its execution history.

Similarly, separate development teams might manage the UI, backend services, or infrastructure through their own Projects, while contributing to the same overall application.

Ideally, I'd like to see:

• Parent/child Project relationships, allowing independently managed Projects to belong to a larger product or initiative.

• Portfolio-level reporting, automatically aggregating progress, status, and completion metrics from child Projects.

• Cross-Project dependency visibility, so dependencies between independently managed teams and deliverables are visible at the parent level.

• Independent Project lifecycles, allowing temporary Projects to be completed and closed without affecting the parent Project.

• Consolidated roadmap views, providing visibility into both ongoing development and finite workstreams without duplicating issues or maintaining separate reporting structures.

GitHub already provides issue hierarchies, sub-issues, dependencies, and multiple Project views. Extending these concepts to Projects themselves seems like a natural evolution.

The primary benefit would be the ability to keep work organized into smaller, independently manageable units while retaining a single, authoritative view of the overall software product.

I'd be interested in seeing either native nested Projects or a portfolio-level abstraction that provides these capabilities.