Jira Metrics

Engineering Flow

AI-first executive view · Custom scope · last 30d

AI Bottom Line

Templated

Throughput declined (-100.0%) and AI participation steady. Not enough samples for AI/Human comparison this period (n<20 across all metrics).

AI ROI: data insufficient for the last 30d. 1 project in scope, none with stable AI vs Human cohort (n≥10 both sides) on Lead Time.
Investigate per project →

Headline KPIs · last 30d

Issues done
0 100.0%
Last 8w
AI participation
0.0%
Last 8w
Lead Time (active)
no trend
Cycle Time (active)
Last 8w

AI insight

  • Where AI helps:Not enough samples for AI/Human comparison this period (n<20 across all metrics)
  • Next focus:Reduce wait time in Ready To Test (currently 114.2d) — this is the team-wide bottleneck.

AI in teams · 0 teams

No teams in scope have AI involvement in this window. As soon as an AI agent assignment, comment, transition, or reporter shows up, this section populates.

Active bottlenecks · top 5

Workflow stageRelative wait timeMedian time
Ready To Test
114.2dp50
In Progress
23.7dp50

Top teams · by throughput

KeyTeamThroughputLead Time (active)Cycle Time (active)Active WIPBlocked WIPAI %
GAMGameLab (Archived)05100%

Data quality amber

Sync freshness1/1 synced
Latest sync1/1 OK
Config coverageall configured
PR linkageno PR data

Report version: engineering-flow.v8 · metric definitions: 2026-05-24.audit18.v1

Period: 2026-08-202026-09-19 · scope: Custom scope (1 project)

Detail view (/overview) → — full per-metric tables, AI Period comparison, longest-stuck list.