Engineering Decision Dashboard

Local-first engineering metrics

Last 8 weeksLocal data

Median PR Cycle Time

PR opened to PR merged

How to read this
Elapsed time from when a pull request is opened until it is merged, shown in hours or days. A high median often means reviews start late or PRs sit idle. A very low median (for example under about 7 minutes) can mean merges happen with little or no review.
No merged PRs in range

Sync failed

PR cycle time exceptions

How to read this
Teams that may need attention in this range: cycle time regressed by at least 25%, stale open PRs crossing the attention threshold, or not enough prior-period merges to compare trends. Up to three exceptions are shown.

16-week PR cycle time comparison trend

How to read this
Previous 8 weeks followed by current 8 weeks. The muted dashed segment is the previous comparison period, the dark segment is the current dashboard period, and gaps mean no merged PRs in that bucket.

The current period has no merged PRs; previous-period history is context, not current performance.

Hours05101520Previous 8 weeksCurrent 8 weeks2.4h15.1h11.7h5h2.4h1.5hJul 10Sep 5Oct 24
  1. previous 2026-07-10: 2.4h
  2. previous 2026-07-17: 15.1h
  3. previous 2026-07-24: 11.7h
  4. previous 2026-07-31: 5h
  5. previous 2026-08-07: 2.4h
  6. previous 2026-08-14: 1.5h
  7. previous 2026-08-21: empty
  8. previous 2026-08-28: empty
  9. current 2026-09-05: empty
  10. current 2026-09-12: empty
  11. current 2026-09-19: empty
  12. current 2026-09-26: empty
  13. current 2026-10-03: empty
  14. current 2026-10-10: empty
  15. current 2026-10-17: empty
  16. current 2026-10-24: empty

Team breakdown

How to read this
Per-team median cycle time and trend versus the previous 8 weeks, based on repository team mapping. Longest open PR shows the oldest still-open pull request for that team.
TeamMerged PRsMedianTrend (vs prev 8 w)Longest Open PR
Aether0——95.9 days
Bevalo0——266.3 days
Csillag0——157.5 days
Design System0——278.2 days
Load Test0——81.6 days
Publication0———
QA0———
Sun0——77.5 days
Sylora0——154.6 days
Turbocsigak0——127.7 days
Unassignedneeds team mapping0——122.7 days

First Review Time

Review latency for merged PRs with submitted reviews

Median First Review Time

How to read this
Elapsed time from when a pull request is opened until the first submitted human review. A high median often means PRs are waiting before review starts.

—

No merged PRs in range

Review-latency exceptions

How to read this
Teams that may need attention in this range: first review latency regressed, PRs merged without qualifying review, or not enough prior-period reviewed PRs exist to compare trends.

None in this range

16-week First Review comparison trend

How to read this
This 16-week chart shows the previous 8-week segment followed by the current 8-week segment. The muted dashed segment is the previous comparison period, the dark segment is the current dashboard period, and gaps mean no qualifying human-reviewed PRs in that bucket.

The current period has no qualifying human-reviewed PRs; previous-period history is context, not current performance.

Hours05101520Previous 8 weeksCurrent 8 weeks2.6h15.8h5.2h2.7h2h1.5hJul 10Sep 5Oct 24
  1. previous 2026-07-10: 2.6h
  2. previous 2026-07-17: 15.8h
  3. previous 2026-07-24: 5.2h
  4. previous 2026-07-31: 2.7h
  5. previous 2026-08-07: 2h
  6. previous 2026-08-14: 1.5h
  7. previous 2026-08-21: —
  8. previous 2026-08-28: —
  9. current 2026-09-05: —
  10. current 2026-09-12: —
  11. current 2026-09-19: —
  12. current 2026-09-26: —
  13. current 2026-10-03: —
  14. current 2026-10-10: —
  15. current 2026-10-17: —
  16. current 2026-10-24: —

Review team breakdown

How to read this
Per-team median first review time and trend versus the previous 8 weeks, based on merged PRs from review-synced repositories.
TeamReviewed PRsFirst ReviewReview TrendNo-review Merges
Aether0———
Bevalo0———
Csillag0———
Design System0———
Load Test0———
Publication0———
QA0———
Sun0———
Sylora0———
Turbocsigak0———
Unassignedneeds team mapping0———