Detected dependencies
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
Unitlane guide
Check Jira group cleanup risk before delete or rename
Review detected direct and derived paths, unknown coverage, and manual checks before using Jira's normal admin controls.
Marketplace trialRead-only reviewCoverage limits
What it does
Preflight reduces blind group-change decisions without claiming universal coverage.
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.
Coverage and 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 keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
No every-access-path guarantee.
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
Coverage remains part of the decision.
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.