Developer Dashboard
Connecting
Date
Repos

All PRs
—
Active
—
Draft
—
Merged
—
Closed
—

Activity

Commits, pull requests, reviews and approvals, GitHub Actions runs and new branches, day by day over the last year. Darker squares mean more activity.

PR Leaderboard

Coder's Championship Standings · all-time · all repos

Lines of Code Leaderboard

Most LoCs · all-time · all repos · all PRs · lockfiles excluded
Pos Contributor Total lines Gap Added Removed

By Repository

Repository All Active Draft Merged Closed

Recent Activity

Open Pull Requests

Date
Project
All projects
Labels
All labels
Priority

Open
—
In Progress
—
In Review & Testing
—
Done
—
Canceled
—

Completed Tickets Leaderboard

Tickets done · avg Ticket Score
PosContributorDoneGapTicket Score

Ticket Quality Leaderboard

Avg Ticket Score of tickets created
PosContributorTicket ScoreGapTickets

Ticket Discipline Leaderboard

Merged PRs linked to a ticket
PosContributorTicketed PRsGapPRs

Activity

Every ticket change (creating, moving, editing, completing) day by day over the last year. Darker squares mean more activity.

Recently Shipped

Features, new development and enhancements finished in this range, newest first.

Trends

Throughput

How many tickets the team finishes each week. The line is the 4-week average, so you can see the pace through busy and quiet weeks.

Created vs Completed

New tickets created vs tickets finished each week. When blue stays above green, the backlog is growing.

Ticket Score Trend

Average Ticket Score of tickets created each week: a clear title (25), a description with real substance (45) and proper labelling, meaning type, project and priority (30). Higher means tickets QA and the QA agent can verify against the code.

Ticket Score Distribution

How many tickets created in this range fall in each Ticket Score band.

Ticketed PRs Trend

Share of merged pull requests each week that are linked to a Linear ticket (via Linear's GitHub link or ENGG-123 in the PR title or branch). Each developer's PRs count from 27 Jul 2026, when the team adopted Linear, or from their own first ticket if later.

Flow Times

Cycle time is start → done; lead time is created → done. Medians, with the time 85% of tickets finish within.

Time in Each Status

Median time tickets spend in each workflow state. Long orange bars are waiting time: work queued for PR, review or testing.

Backlog Health

Tickets waiting in Backlog and Prioritised Backlog at the end of each week, and how old today's backlog is.

Urgent Response

How fast Urgent and High tickets get started, and how much work is started the same day it's created (unplanned work).

Details

Pipeline

Open tickets in each workflow state · Done in range

Projects

Bugs & Hotfixes

Aging Work

Load per Person

Ticket Hygiene

Recent Activity