Skip to content

feat(dashboard): add a Hot tickets overview (#1112) - #1114

Merged
suleimansh merged 2 commits into
mainfrom
feat/hot-tickets
Jul 24, 2026
Merged

feat(dashboard): add a Hot tickets overview (#1112)#1114
suleimansh merged 2 commits into
mainfrom
feat/hot-tickets

Conversation

@suleimansh

Copy link
Copy Markdown
Contributor

Closes #1112

What

A "Hot tickets" overview on the dashboard: a cross-project glance at the tickets that matter right now, in the three lanes Rom asked for.

  • In progress — tickets the agent has planned or spiked
  • Up next — high priority, not started yet
  • Queued — the rest of the open backlog

It pools every project's tickets/ (a new buildHotTickets read + onHotTickets telefunc), so it is a projection of the same files the agent plans from, polled so it stays live. Each row names its project and jumps into it when selected.

Design

Full-width stacked lanes rather than columns, so an uneven split (the common case, where most tickets sit queued) still reads as designed: an empty lane collapses to a single dim header line, a populated one is a clean list of titles with their project, capped with "+N more".

One known gap

There is no run to ticket link, so "being implemented right now" is only approximated by the plan/spike a ticket left. A true "implementing" status would need RunMeta to record the ticket a run started from. Flagged for a follow-up if wanted.

Verification

  • framework 1248 tests (+3 for buildHotTickets / ticketBucket), dashboard 423 tests (+2 for the card), both typechecks + root typecheck clean.
  • Driven in a real browser (light + dark) against a 38-ticket repo.

Add buildHotTickets + an onHotTickets telefunc that pool every project's tickets/
and bucket each into a lane: in-progress (planned or spiked), next (high priority,
not started), or queued (the rest). There is no run to ticket link, so a ticket
being implemented right now is only visible through the plan/spike it left. Exported
through the package surface and the client shim; the telefunc auto-registers.
A cross-project glance at what the agent is working on (planned/spiked), what is
likely next (high priority), and the queued rest. Full-width stacked lanes so an
uneven split still reads as designed: an empty lane collapses to a dim header line,
a populated one is a list of titles with their project, capped with "+N more".
Selecting a ticket jumps into its project (#1112).
@suleimansh suleimansh self-assigned this Jul 24, 2026
@suleimansh
suleimansh marked this pull request as ready for review July 24, 2026 16:43
@suleimansh
suleimansh merged commit ef0d941 into main Jul 24, 2026
1 check passed
@suleimansh
suleimansh deleted the feat/hot-tickets branch July 24, 2026 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add overview of "hot" tickets to dashboard

1 participant