References by source
Detected dependencies are grouped by source so admins know what still depends on the group before delete, rename, replacement, or ownership cleanup.
Unitlane guide
Find where a Jira group is used before delete or rename
Use group preflight and detected references grouped by source.
Marketplace trialClear boundariesNo unsupported guarantees
What it does
Group preflight shows detected references before delete, rename, or replacement.
Severity
High and medium findings help reviewers decide where to look first, especially when a group appears in permissions, shares, workflows, or other supported sources.
Coverage limitations
This point keeps the evaluation practical: what to inspect, why it matters, and what should remain a manual review before any Jira cleanup decision.
What it does not claim
It does not change Jira.
No every-reference claim.
Coverage limits stay visible so reviewers understand what still needs manual checking.
Coverage can be partial.
Partial coverage warns that some references may still require manual inspection, so the scan does not imply more certainty than the available data supports.
Cleanup candidate is not delete-approved.
Cleanup candidates and exports support review; they are not deletion approval.
Best next step
Continue to Group Cleanup Radar for Jira for the current screenshots, evaluation path, trust boundaries, and Marketplace trial link behind this workflow.