Detected references
Detected dependencies are grouped by source so admins know what still depends on the group before delete, rename, replacement, or ownership cleanup.
Unitlane guide
Check Jira group references before delete or rename
Review no detected references in covered sources, unknown coverage, and read-only evidence.
Marketplace trialClear boundariesNo unsupported guarantees
What it does
Preflight reduces blind group cleanup decisions.
Unknown coverage
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
Manual-check areas remain part of the review so the app does not create false confidence.
What it does not claim
It does not delete or rename 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.
No every access path guarantee.
Coverage limits stay visible so reviewers understand what still needs manual checking.
Coverage matrix remains required.
This point keeps the evaluation practical: what to inspect, why it matters, and what should remain a manual review before any Jira cleanup decision.
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.