Jira Metrics

Overview

How the team is doing and where AI is showing up.

? Help
Period
Scope
Filters

Right now · Last 30d

Issues done

77

67.4%

AI participation

0.0%

· 0.0%

Lead Time (active)

6d

21.7%

Cycle Time (active)

1.5d

52.3%

Time to Ready p50

4.3d

10.8%

WIP active

127

13.4%

WIP blocked

32

3.2%

Deploys / week

0.0

Bug rate / week

9.3

9.7%

Trend · last 8 weeks

Throughput

AI %

Cycle Time (active, h)

AI impact

MetricAI medianHuman medianΔ%
Cycle Time (active)AI: n=0Human: 1.5dn=61⚠ n<20
Lead Time (active)AI: n=0Human: 6dn=77⚠ n<20
Time to Ready p50AI: n=0Human: 4.3dn=31⚠ n<20
PRs mergedAI: 0Human: 0
PR review p50AI: n=0Human: n=0⚠ n<20

AI Period Comparison

Not configured for any project in this scope. To compare Before vs After AI, configure an intro_date and modeper project on the project's Configuration page.

Top teams · by throughput

KeyTeamResolved · 30dIssuesAI doneAI %

AI activity · how agents are being used

AgentAssignedAuthored PRsReportedTransitionsComments
Oliver00000
Amelia00000
Anastasia00000
Sakura00000
Nikolaos00000
Veronica (ADOMCPAutomation)00000
Robocop00000
Total00000

Comments will populate as projects re-sync with the new comments fetch.

Data Quality

CheckStatusCurrent valueWhat it means
Sync freshness1/1 projects · 1 stale > 24h · oldest PU 298.8hHow recently we pulled JIRA data. Stale > 24h means the numbers in this scope may be lagging real-world state.
Latest sync status1/1 projects last sync OKWhether each project's most recentsync succeeded. This is the current-health signal: if green, every project's data is fresh from a successful pull, even if older runs in the 24h window failed.
Historical errors (last 24h)0Count of failed sync attempts in the last 24h. Transient noise unless Latest sync status above is also red — then a project is currently broken, not just blipped.
Metric configsall projects fully configuredEach project has 11 metric definitions (start/end statuses, ready statuses, etc.). All projects fully configured means cycle/lead/WIP/throughput/etc. use the project-specific status lists, not fallback defaults.
AI Period coverage0/1 projects configuredNumber of projects where someone clicked 'Compare' on the project's config page and set an AI introduction date. Drives the 'Before vs After AI' section below. Most projects can stay unconfigured — only opt in for projects where you actually want a before/after split.
Stage config coverageall observed statuses configured · all wip configs include pause statusesConfigs must list every status the team actually uses. Otherwise Where Work Waits and Blocked WIP silently drop transitions. Audit17 P0-3.
PR ↔ JIRA linkage (last 30d)no completed PRs in 30dShare of completed PRs whose branch name or title contains a JIRA issue key (e.g. ADS-1234). Below 60% means the PR/JIRA join is unreliable for that project — for those, quote PR-only metrics (PR Throughput, Review Duration) instead of metrics that join PRs back to JIRA tickets.

Where work waits

Bottleneck: tickets spend the most time in Waiting for Client (331.8d median). This is the top of Active Flow Bottlenecks, not the intake card.

Active Flow Bottlenecks

Workflow stageRelative wait timeMedian time
Waiting for Client
331.8dp50
On Hold
158.9dp50
Failed On Testing
85.9dp50
Ready For Live
68.6dp50
Ready For Review
45.4dp50
In Progress
2.2dp50

Backlog / Intake Aging

Workflow stageRelative wait timeMedian time
New
241.8dp50
Approved for Sprint
149.1dp50
Approved
9.8dp50
To Do
9.5dp50

Longest stuck right now

KeySummaryStatusAge
PU-1698 Ball Pool Together - launch stand-alone 8 ball Pool TogetherIn Progress727.6d
PU-126Premier Sunday Crossword - Solve source of puzzle feedsReady For Live727.6d
PU-177Crosswords - high priority maintenance and improvementsIn Progress727.6d
PU-81AARP all games - adaptive samplingReady For Review727.6d
PU-95Let's Block Champ - Release Request 15Failed On Testing727.6d
PU-151Outspell - Core GameplayReady To Test727.6d
PU-161Outspell - SoundsReady To Test727.6d
PU-170Outspell - UI Preloader ScreenReady To Test727.6d