Overview
How the team is doing and where AI is showing up.
Period
Scope
Filters
Right now · Last 30d
Issues done
8
▼ 38.5%
AI participation
0.0%
· 0.0%
Lead Time (active)
4.4d
▲ 46.6%
Cycle Time (active)
4.9d
▲ 288.7%
Time to Ready p50
2.5h
▼ 96.4%
WIP active
61
▲ 1.7%
WIP blocked
11
· 0.0%
Deploys / week
0.0
▼ 100.0%
Bug rate / week
0.0
—
Trend · last 8 weeks
Throughput
AI %
Cycle Time (active, h)
AI impact
MetricAI medianHuman medianΔ%
Cycle Time (active)AI: —n=0Human: 4.9dn=6⚠ n<20
Lead Time (active)AI: —n=0Human: 4.4dn=8⚠ n<20
Time to Ready p50AI: —n=0Human: 2.5hn=6⚠ 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 | 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 TECH 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 On Hold (636.7d median). This is the top of Active Flow Bottlenecks, not the intake card.
Active Flow Bottlenecks
Workflow stageRelative wait timeMedian time
On Hold
636.7dp50
Ready For Review
343.5dp50
Ready To Test
34.5dp50
Ready For Live
32.3dp50
In Testing
8.4dp50
In Progress
5.2dp50
Backlog / Intake Aging
Workflow stageRelative wait timeMedian time
New
420.7dp50
Approved
39.4dp50
Approved for Sprint
2.2dp50
Longest stuck right now
| Key | Summary | Status | Age |
|---|---|---|---|
| TECH-68 | [Server-to-Server payment notification] add api for reading failed transaction list | Ready For Live | 752.6d |
| TECH-171 | Authentication process in Nakama will now fetch gem count from Eagle on user creation | Ready To Test | 732.4d |
| TECH-186 | [Dual Sync Approach] Eagle side synchronization | Ready For Live | 727.6d |
| TECH-247 | [Stretch] Setup Load Testing on Nakama Instances Using Hearts Game | In Progress | 633.5d |
| TECH-330 | Investigate the usage of Inventory Feature on Hiro | Ready For Review | 602.5d |
| TECH-331 | Move SDK documentation/sandbox site to developers.arkadium.com | Ready For Review | 598.5d |
| TECH-349 | Prevent Devs from sending Custom Analytics Events through the SDK | Ready To Test | 595.6d |
| TECH-340 | Investigate the usage of Achievements Feature on Hiro | Ready For Review | 593.4d |