Direct 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
Find where a Jira group is used before you change it
Use the group view to inspect detected source objects, available derived permission paths, severity, and coverage.
Marketplace trialRead-only reviewCoverage limits
What it does
Group Cleanup Radar works backward from the selected group across supported Jira sources.
Derived role-to-permission paths
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
Severity and Jira destinations
High and medium findings help reviewers decide where to look first, especially when a group appears in permissions, shares, workflows, or other supported sources.
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, failed, unavailable, or manual-check.
Partial coverage warns that some references may still require manual inspection, so the scan does not imply more certainty than the available data supports.
No detected reference is not universal approval.
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
Best next step
Continue to Group Cleanup Radar for Jira for the current screenshots, trust boundaries, docs, and Marketplace trial link behind this workflow.