Dependency Map improvements for archived projects and Xray data visibility

Description

Add visibility of total Xray data values in the downloadable Dependency Map to improve migration analysis and dependency validation. Additionally, archived projects should appear connected to their respective groups in the Dependency Map. If an archived project is independent and not connected to a group, it should still display its associated Xray data.

User friction

Customers currently lack visibility into the amount of Xray data associated with projects in the downloadable Dependency Map, making it difficult to assess migration complexity and identify potential risks. Archived projects are also not clearly represented, which may lead to incomplete dependency analysis and unexpected migration behavior.

Steps to reproduce (right now) / Actual Result:

Generate and download the Dependency Map.
Review projects with Xray data associations.
Review archived projects and their relationships.

Actual Result:

The downloadable Dependency Map does not display total Xray data values.
Archived projects may not appear connected to their respective groups.
Independent archived projects do not clearly show associated Xray data.

IMPACT

What would improve if solved:

Improved visibility into Xray data distribution and migration scope.
Easier identification of high-risk or high-volume projects before migration.
Better understanding of archived project dependencies and associations.
More accurate migration planning and troubleshooting.

Impact on stakeholders:

Customers gain better visibility and confidence during migration preparation.
Support and migration teams can more easily identify dependency-related risks.
Reduces confusion during migration validation and investigation processes.
Helps stakeholders make informed decisions regarding archived and independent projects.

Current workaround:
Customers and support teams must manually validate project relationships and estimate Xray data associations outside of the Dependency Map, which is time consuming and error prone.

CONTEXT & EXAMPLES:

The issue becomes particularly relevant in large migration scenarios where archived projects still contain relevant Xray data or hidden dependencies. Missing visibility may lead to migration inconsistencies or unexpected failures during validation and execution.

Concrete example:

An archived project contains Xray entities linked to a migration group, but the downloadable Dependency Map does not show the association. In another scenario, an independent archived project contains Xray data but appears disconnected or without visibility into the associated data volume.

Workaround risk:

Manual validation increases the risk of overlooking dependencies, underestimating migration scope, or missing archived projects that still contain relevant Xray data, potentially leading to failed or incomplete migrations.

Guidelines images: