Drilling into a person or a ticket
A widget's tile is an aggregate. When you need the rows behind it — every PR from one developer, or every event on one ticket — Deckgauge gives you two separate ways in.
Clicking a developer row opens this board's console, pre-filtered to that author.
Click a widget row: filter the underlying query
On widgets that list or plot individual developers — Merge Frequency per Developer and PR Cycle Time Scatter among them — clicking a row or a point opens this board's Intelligence console (the SQL editor tab) with that widget's own query pre-loaded and filtered to the value you clicked, e.g. narrowed to one author. Your current period-picker selection carries over into the console. This is the fastest way to go from "who's driving this number" to the exact rows.
Two board-scoped pages
Deckgauge also ships two standalone, board-scoped views you can navigate to directly:
/boards/[boardId]/insights/developers— a leaderboard of every author on this board's connected sources, ranked by AI-assisted PR percentage over the last 30 days, with each row showing PRs, AI %, and a link back to the board./boards/[boardId]/insights/tickets/[key]— a single ticket's unified timeline. It merges Jira status transitions with every GitHub/GitLab/ADO pull request and commit that references the ticket key, in chronological order, each entry tagged with its source.
Both are scoped to whatever this board has connected — a source available on another board doesn't leak in. Neither page is currently linked from a widget click; open them directly by URL, substituting your board's id and, for the ticket view, the ticket's key (e.g. PLAT-482).
If it looks wrong
| Symptom | Cause | Fix |
|---|---|---|
| Developers page says "No intelligence sources connected" | This board has no Jira/GitHub/ADO/GitLab source attached | Connect one on the board's Sources tab |
| Ticket timeline is empty for a key you know is active | None of this board's connected sources reference that key, or the referencing source isn't connected to this board | Confirm the source is attached to this board, not only another one |
| Clicking a widget row does nothing | That widget type doesn't support a filtered drill (most trend/aggregate widgets don't) | Use the Intelligence console directly for ad-hoc queries |
Related
- Filters & date ranges — the period that carries into a filtered console view.
- How a widget gets its number — why a drilled-down view can still come back empty.
- Merge Frequency per Developer — one of the widgets a person-level drill starts from.
Last updated