Jira Metrics

Engineering Flow

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

AI Bottom Line

AI-narratedcached· 2026-07-21 00:29 UTC

In the last 30 days, GameLab 2.0 showed no completed work or deployments, while 2 items remained active and the visible flow constraint sat in In Progress.

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
no trend
AI participation
0.0%
no trend
Lead Time (active)
no trend
Cycle Time (active)
no trend

AI insight

  • Where AI helps:No AI-owned work was recorded, so there is no evidence of measurable help in this window.
  • Where AI hurts:AI is not contributing to current delivery outcomes in scope; participation and AI-owned share are both 0%.
  • Next focus:Review the two long-running In Progress investigations and either unblock, narrow scope, or exit them to restore movement.

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

Not enough transition data yet — sync a few projects to populate.

Top teams · by throughput

KeyTeamThroughputLead Time (active)Cycle Time (active)Active WIPBlocked WIPAI %
GLGameLab 2.00200%

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-06-222026-07-22 · scope: Custom scope (1 project)

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