ADO Test Plan Hierarchy Not Readable by GHC

[dhanveer16]

Description
The Azure DevOps (ADO) MCP currently fails to accurately interpret and represent the hierarchical structure of test plans. In ADO, test plans are organized as:
Test Plan → Root Suite → Parent Suite → Sub-suite → Test Cases

However, this hierarchy is not properly maintained or exposed through the platform or its APIs. As a result, the QA team faces significant challenges in managing and tracking test cases effectively.
Impact

Traceability Issues: The inability to preserve the folder and subfolder hierarchy makes it difficult to trace test cases back to their respective suites and parent structures.
Workflow Disruption: QA rely on this hierarchy for organizing test cases logically. Losing this structure impacts planning, execution, and reporting workflows.

Expected Behavior

The MCP should correctly interpret and expose the full hierarchy of test plans, including all nested suites and their relationships.

Current Behavior

Hierarchical relationships are flattened or lost when accessed via MCP or API.
Exports fail to represent the nested structure, leading to manual workarounds.

Suggested Solution

Enhance MCP and API capabilities to:

Preserve and expose the full hierarchy of test plans and suites.
Include parent-child relationships in data models and exports.

[danhellem]

As noted in other thread, the tools are just using the public rest apis. The change you are requesting would require new or updated APIs. We currently do not have plans to do so.