Overview
How the team is doing and where AI is showing up.
Period
Scope
Filters
Right now · Last 30d
Issues done
52
▼ 54.8%
AI participation
0.0%
▼ 11.3%
Lead Time (active)
4.6d
▼ 66.3%
Cycle Time (active)
2.1d
▼ 68.7%
Time to Ready p50
1.3d
▼ 19.9%
WIP active
44
▲ 46.7%
WIP blocked
5
· 0.0%
Deploys / week
0.0
—
Bug rate / week
1.4
· 0.0%
Trend · last 8 weeks
Throughput
AI %
Cycle Time (active, h)
AI impact
MetricAI medianHuman medianΔ%
Cycle Time (active)AI: —n=0Human: 2.1dn=52⚠ n<20
Lead Time (active)AI: —n=0Human: 4.6dn=52⚠ n<20
Time to Ready p50AI: —n=0Human: 1.3dn=52⚠ n<20
PRs mergedAI: 0Human: 0—
PR review p50AI: —n=0Human: —n=0⚠ n<20
Before vs After AI
| Metric | Before AI | After AI | Δ |
|---|---|---|---|
| Lead time p50 (raw, days) | 15.3dn=2212 | 11dn=513 | ▼ 28.4% |
| Throughput / week | 21.4n=2212 | 21.1n=513 | ▼ 1.4% |
| AI participation (%) | 0n=2212 | 20.5n=513 | — |
| Deploys / week | —n=0 | —n=0 | ⚠ |
| Change failure rate (%) | —n=0 | —n=0 | ⚠ |
Per-project breakdown (1 project)
mode: compare
Before AI103 weeks · n=2212
- Lead Time (raw)
- 15.3d
- Throughput / wk
- 21.4
- AI %
- 0%
- Deploys / wk
- —
- Change fail rate
- —
- Deployments
- 0
After AI24 weeks · n=513
- Lead Time (raw)
- 11d
- Throughput / wk
- 21.1
- AI %
- 20.5%
- Deploys / wk
- —
- Change fail rate
- —
- Deployments
- 0
Tip: switch any project to Before only / After only in its config to focus on one era — useful when one side has insufficient data or contaminated history.
Top teams · by throughput
KeyTeamResolved · 30dIssuesAI doneAI %
AI activity · how agents are being used
| Agent | Assigned | Authored PRs | Reported | Transitions | Comments |
|---|---|---|---|---|---|
| Oliver | 0 | 0 | 0 | 0 | 0 |
| Amelia | 0 | 0 | 0 | 0 | 0 |
| Anastasia | 0 | 0 | 0 | 0 | 0 |
| Sakura | 0 | 0 | 0 | 0 | 0 |
| Nikolaos | 0 | 0 | 0 | 0 | 0 |
| Veronica (ADOMCPAutomation) | 0 | 0 | 0 | 0 | 0 |
| Robocop | 0 | 0 | 0 | 0 | 0 |
| Total | 0 | 0 | 0 | 0 | 0 |
Comments will populate as projects re-sync with the new comments fetch.
Data Quality
| Check | Status | Current value | What it means |
|---|---|---|---|
| Sync freshness | ⚠ | 1/1 projects · 1 stale > 24h · oldest EVO 402.2h | 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 | ✓ | 1/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 On Hold (17.2d median). This is the top of Active Flow Bottlenecks, not the intake card.
Active Flow Bottlenecks
Workflow stageRelative wait timeMedian time
On Hold
17.2dp50
Waiting for Client
16.2dp50
Ready For Staging
4.5dp50
PM/Client Review
2.7dp50
Ready For Review
22.2hp50
Ready For Canary
20.1hp50
Backlog / Intake Aging
Workflow stageRelative wait timeMedian time
Approved
204.2dp50
New
47.1dp50
Backlog
43.9dp50
To Do
25.1dp50
Selected for Development
0.2hp50
Longest stuck right now
| Key | Summary | Status | Age |
|---|---|---|---|
| EVO-3212 | [Q1 | 2026] On Call Issues - Sentry / Grafana | In Progress | 389.1d |
| EVO-3438 | [Unit-Tests] Cover missing important areas | In Progress | 240d |
| EVO-3807 | [2026] MSFT Trivia Arena | In Progress | 184.8d |
| EVO-3875 | [2026] Bugs - UI | In Progress | 184.8d |
| EVO-3876 | [2026] Bugs - General | In Progress | 184.8d |
| EVO-3873 | [2026] Microsoft bugs | In Progress | 184.8d |
| EVO-3857 | [2026] Bugs - Data | In Progress | 184.8d |
| EVO-3590 | [Q1 - Q?| 2026] EVO performance improvements | In Progress | 184.8d |
133 tickets excluded — managed centrally.