Drift is the gap between what the tracker says and what the code shows. Every row below is a
disagreement GroundTruth found by reading source control and comparing it to the ticket.
Each finding carries a confidence. That number is not drift and it is not a quality score: it is
how certain the check is about this one judgment. A finding above the threshold can be applied
automatically. Below it, nothing is written and the finding goes to a person with the criterion
and the diff side by side, because a wrong write costs more than a slow one.
The common cases are a ticket in Done with nothing merged behind it, work that merged against no
ticket at all, and a ticket whose acceptance criteria are not met by the code that closed it.
Drift & findings
GitHub ground truth vs. Jira. High-confidence items auto-apply in live mode; the rest are proposed for a human.
Severity
Type
Ticket
PRs
Finding
Confidence
high
merged-not-done
ENG-812
#1204
PR merged but ticket is "In Progress"
95%
high
cross-team-dependency
ENG-820
-
Needs identity API from INIT-4 (PR #1177, not merged) - Checkout blocked on Identity
80%
medium
stale-in-review
ENG-777
#1190
In Review but PR merged 4d ago
85%
medium
orphan-pr
-
#1206
PR #1206 is not linked to any ticket (untracked work)
80%
medium
stalled
ENG-731
-
In Progress with no PR and no update for 14d
70%
medium
stale-rollup
EPIC-51
-
All children of EPIC-51 are done but EPIC-51 is "In Progress"
80%
low
assignee-mismatch
ENG-760
#1188
Ticket assignee "Sam Okoro" is not a PR author (Priya Rao)
50%
PR → ticket links
Inferred by the linker. Orphans (no ticket) surface as untracked work.
PR
Ticket
Signal
Confidence
#1204
ENG-812
branch
90%
#1198
ENG-799
closes-directive
98%
#1190
ENG-777
title
85%
#1188
ENG-760
commit
80%
#1206
orphan
-
-
Finish setting up GroundTruth
A couple of steps and GroundTruth starts keeping your Jira true.