As a user, I can define a Test Plan as including other Test Plans

Description
As a user, I would like to define a Test Plan that includes other Test Plans, so that I can have a consolidated overview of multiple related Test Plans.

This would allow hierarchical test management and make it easier to monitor progress and results across several Test Plans from a single parent Test Plan.

Example:

• Adding a Test to a sub Test Plan would automatically reflect in the parent Test Plan.
• Adding a Test Execution to a sub Test Plan would also appear in the parent Test Plan.

User friction
Currently, users cannot group or aggregate multiple Test Plans into a parent Test Plan. This makes it difficult to track testing progress across teams, components, or environments and requires manual consolidation.

Steps to reproduce (right now) / Actual Result:

1. Create multiple Test Plans for different scopes (e.g., teams or components).
2. Add Tests and Test Executions to those Test Plans.
3. Attempt to create a higher-level Test Plan that aggregates them.

Actual Result:
There is no native way to include Test Plans inside another Test Plan.

IMPACT
Large projects often split testing across several Test Plans, making it difficult to monitor overall testing progress or provide consolidated reporting.

What would improve if solved:

• Centralized visibility of multiple Test Plans
• Easier tracking of testing progress at release or program level
• Reduced manual reporting effort

Impact on stakeholders:

• QA Managers: better high-level progress visibility
• Test Leads: easier coordination across teams
• Stakeholders: clearer understanding of release readiness

Current workaround:
Use Document Generator to create reports that aggregate information from multiple Test Plans.

CONTEXT & EXAMPLES
Concrete example:
A release may have separate Test Plans for Frontend, Backend, Mobile, and Integration testing. A parent Test Plan could aggregate these and provide a unified overview of testing progress.

Workaround risk:
Document Generator reports are static and require manual generation, which can lead to outdated information and additional maintenance effort.