Detected direct and derived paths
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
Change or retire a Jira group with evidence in view
Scan all groups, inspect the selected group's detected impact, record the plan, change Jira manually, and Recheck the result.
Marketplace trialRead-only reviewCoverage limits
What it does
Group Cleanup Radar connects the before-state, intended change, fresh supported-source scan, and coverage boundary.
Delete, Replace, Retire, or Investigate plan
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
Coverage-aware Recheck
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
What it does not claim
It does not make the Jira change.
No universal safe-to-delete claim.
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
Failed or partial sources remain explicit.
Partial coverage warns that some references may still require manual inspection, so the scan does not imply more certainty than the available data supports.
Selected-group Watch is opt-in.
Keep proposed changes in a reviewable action plan before applying anything, with selected rows, skips, and estimated impact visible in one place.
Best next step
Continue to Group Cleanup Radar for Jira for the current screenshots, trust boundaries, docs, and Marketplace trial link behind this workflow.