Jira Metrics

Overview

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

? Help
Period
Scope
Filters

Right now · Last 30d

Issues done

21

61.8%

AI participation

0.0%

· 0.0%

Lead Time (active)

24d

7.9%

Cycle Time (active)

4d

53.1%

Time to Ready p50

19.9d

183.3%

WIP active

28

16.7%

WIP blocked

18

· 0.0%

Deploys / week

0.5

150.0%

Bug rate / week

0.7

86.3%

Trend · last 8 weeks

Throughput

AI %

Cycle Time (active, h)

AI impact

MetricAI medianHuman medianΔ%
Cycle Time (active)AI: n=0Human: 4dn=21⚠ n<20
Lead Time (active)AI: n=0Human: 24dn=21⚠ n<20
Time to Ready p50AI: n=0Human: 19.9dn=21⚠ n<20
PRs mergedAI: 0Human: 14
PR review p50AI: n=0Human: 5.4dn=6⚠ 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
Nikolaos000051
Oliver01073
Amelia00000
Anastasia00000
Sakura00000
Veronica (ADOMCPAutomation)00000
Robocop00000
Total010754

Data Quality

CheckStatusCurrent valueWhat it means
Sync freshness1/1 projects · 1 stale > 24h · oldest TDOT 298.3hHow 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)TDOT 85.7% (12/14)Share 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 Failed On Testing (1.5d median). This is the top of Active Flow Bottlenecks, not the intake card.

Active Flow Bottlenecks

Workflow stageRelative wait timeMedian time
Failed On Testing
1.5dp50
On Hold
1.4dp50
In Progress
17.4hp50
Ready For Live
4.7hp50
Ready To Test
1.4hp50
CODE REVIEW
1.2hp50

Backlog / Intake Aging

Workflow stageRelative wait timeMedian time
New
27.3dp50
Selected for Development
2.1dp50
Backlog
2.1dp50

Longest stuck right now

KeySummaryStatusAge
TDOT-342[Game][Klondike Solitaire] Add "no more moves" stateFailed On Testing250.2d
TDOT-6[Game] Spider SolitaireIn Progress248.4d
TDOT-642Phase 2In Progress193.6d
TDOT-650[Platform] Content Management UpdatesIn Progress186.3d
TDOT-39[Game] Pyramid SolitaireIn Progress94.3d
TDOT-648[Game] Solvable Seeds IdentificationIn Progress94.3d
TDOT-775No More Moves improvementsIn Progress94.3d
TDOT-843Review and update packages with Trivy-reported vulnerabilitiesReady To Test88.8d