Anatomy of a ticket

Range:

Validation & drill-down view. Use this page to understand exactly how each flow metric is computed for one project, and where the AI cohort differs from the human cohort. Headline numbers on /flow and /overview roll up the same formulas across all projects. Hover any lane label for the formula and a sample-size note.

Anatomy of a ticket — PDO

Window: 30d · All 14 · AI 1 · Human 13

Jira Flow Lead Time (raw / wall-clock)

27.4dn=14AI63.7dn=1 · directionalH26.0dn=13

Lead Time (active, ÷ pauses)

19.4dn=14AI41.1dn=1 · directionalH18.0dn=13

Time to Ready

20.8dn=13AI1.8hn=1 · directionalH20.8dn=12

Cycle Time (raw / wall-clock)

11.7dn=14AI63.7dn=1 · directionalH11.5dn=13

Lead Time for Changes

Not enough data in this window

Cycle Time (active, ÷ pauses)

185hn=14AI41.1dn=1 · directionalH181hn=13

Time to First PR

Not enough data in this window

PR Review Duration

Not enough data in this window

Created

Ready

In Progress

In Review

Done

Deployed

AI vs Human comparison

Bars proportional within each row (max = 100%). Δ% lower-is-better — green = AI faster.

Jira Flow Lead Time (raw / wall-clock)

Created → Done · wall-clock hours including weekends and pauses

directionalView tickets (1/13) →

63.7d n=1 · dir.

Human

26.0d n=13

Lead Time (active, ÷ pauses)

Created → Done · business hours minus configured pause statuses

directionalView tickets (1/13) →

41.1d n=1 · dir.

Human

18.0d n=13

Time to Ready

Created → first transition into a ready status (Selected / Approved / Ready)

directionalView tickets (1/12) →

1.8h n=1 · dir.

Human

20.8d n=12

Cycle Time (raw / wall-clock)

First cycle-start status → Done · wall-clock hours

directionalView tickets (1/13) →

63.7d n=1 · dir.

Human

11.5d n=13

Cycle Time (active, ÷ pauses)

First cycle-start status → Done · business hours minus pauses

directionalView tickets (1/13) →

41.1d n=1 · dir.

Human

181h n=13

Not measurable (one cohort has zero samples):

·Time to First PR — no tickets / PRs measurable in this window
·PR Review Duration — no tickets / PRs measurable in this window
·Lead Time for Changes — no tickets / PRs measurable in this window

Cohort breakdown

⚠ marker when AI or Human cohort sample size is below 10.

Metric	All p50	n	AI p50	n	Human p50	n	Δ (AI vs Human)
Jira Flow Lead Time (raw / wall-clock)	27.4d	14	63.7d	1 ⚠	26.0d	13	—
Lead Time (active, ÷ pauses)	19.4d	14	41.1d	1 ⚠	18.0d	13	—
Time to Ready	20.8d	13	1.8h	1 ⚠	20.8d	12	—
Cycle Time (raw / wall-clock)	11.7d	14	63.7d	1 ⚠	11.5d	13	—
Cycle Time (active, ÷ pauses)	185h	14	41.1d	1 ⚠	181h	13	—
Time to First PR	—	0	—	0 ⚠	—	0 ⚠	—
PR Review Duration	—	0	—	0 ⚠	—	0 ⚠	—
Lead Time for Changes	—	0	—	0 ⚠	—	0 ⚠	—

All = every measurable ticket / PR in the window. AI = agent-owned cohort (ticket assignee or PR author is an active agent at completion). H = human cohort (everyone else, including unassigned). Δ compares AI vs Human p50 — negative = AI faster.

Side metrics

Throughput / week

3.3

AI 0.2 · H 3.0

WIP — Active now

Blocked 6

Bug rate / week

0.0

no bugs in window

AI participation

AI 1 / 14

Top bottleneck

Ready For Live

median 12.9d

Deploys / week

0.0

ADO-style

Change failure rate

—

no ADO mapping

PR acceptance

—

no PRs in window

🧠 AI deep analysis

Generate an LLM-driven explanation of WHY the AI cohort is faster / slower on each lane. Cites specific tickets from the evidence pack, suggests next steps.

Active variants use business hours minus pause statuses (same formula as the per-project Cycle / Lead pages). Raw variants are pure wall-clock. AI cohort = ticket assignee (or PR author) is an active agent at completion time. Sample-size suppression marks values directional only when AI or Human cohort drops below 10 — the value is still shown for context but trust it less.

4 auto-filtered zombies (1 idle · 3 direct · 3 old) — Rules