Overview
How the team is doing and where AI is showing up.
Period
Scope
Filters
Right now · Last 30d
Issues done
12
—
AI participation
75.0%
▲ 75.0%
Lead Time (active)
3.1d
—
Cycle Time (active)
1.3d
—
Time to Ready p50
0.1h
—
WIP active
2
—
WIP blocked
0
—
Deploys / week
0.0
—
Bug rate / week
0.7
—
Trend · last 8 weeks
Throughput
AI %
Cycle Time (active, h)
AI impact
MetricAI medianHuman medianΔ%
Cycle Time (active)AI: 3dn=9Human: 11.1hn=3⚠ n<20
Lead Time (active)AI: 3.1dn=9Human: 1.6dn=3⚠ n<20
Time to Ready p50AI: 0.1hn=9Human: 0.1hn=3⚠ 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
| Agent | Assigned | Authored PRs | Reported | Transitions | Comments |
|---|---|---|---|---|---|
| Oliver | 9 | 0 | 0 | 98 | 147 |
| Nikolaos | 0 | 0 | 0 | 0 | 35 |
| Amelia | 0 | 0 | 0 | 0 | 0 |
| Anastasia | 0 | 0 | 0 | 0 | 0 |
| Sakura | 0 | 0 | 0 | 0 | 0 |
| Veronica (ADOMCPAutomation) | 0 | 0 | 0 | 0 | 0 |
| Robocop | 0 | 0 | 0 | 0 | 0 |
| Total | 9 | 0 | 0 | 98 | 182 |
Data Quality
| Check | Status | Current value | What it means |
|---|---|---|---|
| Sync freshness | ⚠ | 1/1 projects · 1 stale > 24h · oldest TAA 298.3h | How recently we pulled JIRA data. Stale > 24h means the numbers in this scope may be lagging real-world state. |
| Latest sync status | ✓ | 1/1 projects last sync OK | Whether 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) | ✓ | 0 | Count 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 configs | ✓ | all projects fully configured | Each 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 coverage | ⚠ | 0/1 projects configured | Number 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 coverage | ✓ | all observed statuses configured · all wip configs include pause statuses | Configs 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 30d | 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 Ready For Review (1.4d median). This is the top of Active Flow Bottlenecks, not the intake card.
Active Flow Bottlenecks
Workflow stageRelative wait timeMedian time
Ready For Review
1.4dp50
On Hold
1dp50
In Progress
10.5hp50
CODE REVIEW
0hp50
Ready To Merge
0hp50
In Deployment
0hp50
Backlog / Intake Aging
Workflow stageRelative wait timeMedian time
Selected for Development
2.1hp50
Backlog
0hp50