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.
Unitlane guide
Record the plan and Recheck the result
Save the before-state, make the Jira change through normal admin controls, then run a fresh coverage-aware scan against the intended outcome.
Marketplace trialRead-only reviewCoverage limits
What it does
Recheck records whether supported paths changed as planned, remain, changed differently, or are unknown because coverage was insufficient.
Saved before-state
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 verdict
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
The app does not make the Jira change.
A failed or partial source cannot prove a path was removed.
Partial coverage warns that some references may still require manual inspection, so the scan does not imply more certainty than the available data supports.
Unknown remains explicit.
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
The administrator owns the final 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.