Included records
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
Read source status and caveats
Source status keeps the weak spots visible, especially when a reviewer needs to know what could not be verified from collected records.
Marketplace trialJSM request contextCaveats preserved
What it does
Source status labels help reviewers distinguish included records, unavailable records, outside-scope records, and caveats preserved for handoff.
Unavailable sources
Unavailable sources are labeled instead of being treated as clear, keeping coverage limits visible before an admin changes Jira.
Preserved caveats
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 imply that an unavailable source was checked successfully.
No silent pass for missing evidence.
Preserve the detected references, blockers, and coverage notes for later review when cleanup needs approval, audit follow-through, or admin handoff.
No every-source coverage claim.
This keeps the review practical: what to inspect, why it matters, and what should remain a manual check before any Jira cleanup decision.
No unsupported attestation.
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 Request Evidence Control for JSM for the current screenshots, trust boundaries, docs, and Marketplace trial link behind this workflow.