Group Cleanup Radar
See groups in one table with member counts, cleanup status, reference counts, risk tags, and coverage confidence.
Group Cleanup Radar scans Jira groups and detected references so admins can find cleanup candidates, blockers, empty groups, and unknown coverage before deleting, renaming, or replacing a group.
Instead of guessing which group to inspect, run the radar first. See cleanup candidates, referenced groups, empty groups, high-risk groups, and unknown coverage in one place.
Cleanup candidate means no detected references were found in covered sources. It is not deletion approval. Always review the coverage matrix and manual-check areas before changing Jira.
Read-only discovery for group cleanup decisions.
See groups in one table with member counts, cleanup status, reference counts, risk tags, and coverage confidence.
Before delete, rename, or replacement, inspect one group's references by source and severity.
Avoid false confidence by separating covered, partially covered, unavailable, and manual-check sources.
Spot likely cleanup candidates and do-not-touch groups without manually bouncing across Jira screens.
Export cleanup reports and evidence when review, handoff, or audit follow-through matters.
Each screenshot shows one value moment: all-groups radar, group preflight, and coverage honesty.

Group Cleanup Radar ranks groups by cleanup status, references, member count, risk tags, and coverage confidence.

Group preflight shows detected references, blockers, severity, and why each dependency matters before cleanup.

The coverage matrix separates covered, partially covered, unavailable, and manual-check sources to avoid false confidence.
Run the radar scan, filter cleanup candidates and empty groups, open one group preflight, review detected references and unknown coverage, then export a report if another reviewer needs the cleanup story.
No. It is read-only and does not delete groups, rename groups, modify permissions, edit workflows, or change Jira configuration.
No. It means no detected references were found in covered sources. Always review coverage and manual-check areas before a Jira change.
Yes. The radar scan ranks cleanup candidates, referenced groups, empty groups, and unknown coverage.
Verified coverage includes project roles, permission schemes, filter shares, dashboard shares, issue security, and workflow references/properties where available. Queues, automation, app-specific areas, unsupported areas, and partial areas are shown as manual check, unavailable, or partial coverage.