Group inventory
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
Start with all groups, then open the group connected to the change you need to make.
The radar scan separates likely cleanup candidates, detected blockers, member signals, and unknown coverage.
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
Detected dependencies are grouped by source so admins know what still depends on the group before delete, rename, replacement, or ownership cleanup.
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
A cleanup candidate is not universally delete-approved.
Coverage limits stay visible so reviewers understand what still needs manual checking.
Manual-check areas remain part of the review so the app does not create false confidence.
Group Cleanup Radar scans and reports findings only; it does not delete, rename, edit permissions, or change Jira configuration.
Continue to Group Cleanup Radar for Jira for the current screenshots, trust boundaries, docs, and Marketplace trial link behind this workflow.