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
Open group preflight
Use preflight to inspect detected references grouped by source and severity.
Marketplace trialClear boundariesNo unsupported guarantees
What it does
Group preflight shows detected references and blockers for one group.
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.
Why dependencies matter
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 delete, rename, or change groups.
No safe-to-delete guarantee.
This point keeps the evaluation practical: what to inspect, why it matters, and what should remain a manual review before any Jira cleanup decision.
Unknown coverage must be reviewed.
Manual-check, unavailable, and partial areas stay visible so reviewers do not overtrust the scan or assume missing data means the group is unused.
Manual checks may remain.
Manual-check areas remain part of the review so the app does not create false confidence.
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.