Concepts
Roadmap and work timeline
What is moving, who worked when, who waited on what, and which tickets have stalled.
The Roadmap
A project’s Roadmap shows its tickets in an active, blocked or review stage, last updated first, each with its tasks and its lanes. Under each row it draws the ticket’s work timeline.
The work timeline
Agents record their work on a ticket as they go:
- Spans: a phase of work, such as spec, build, a review round, verify, PR, preview or merge.
- Waits: time an agent could not go on, with a reason: a shared lock, another agent’s result, the board or an MCP server down, you, or something else.
- Hand-offs: work passing from one agent to another, a subagent included.
- Heartbeats: “still working”, every few minutes.
The board adds what it sees itself: pushes to the ticket’s branch, its PR being opened and merged, its preview’s states and every move between stages.
On the Roadmap, spans are segments by phase, waits are hatched with their reason, hand-offs are markers and the board’s own events are dots. The ticket page has a Timeline card with the same bar and the list of events. None of this goes to the ticket’s feed or the Daily view.
Totals
Per ticket and per project, the timeline adds up three totals that never overlap:
- Blocked on you: waits on you, and time in a blocked stage.
- Waiting: every other wait.
- Working: spans outside those, overlapping spans counted once.
Stalled tickets
A ticket in an active stage with no event of any kind for longer than the project’s stall time (30 minutes by default, set in the project’s settings) reads as stalled: on its card, on the Roadmap, in the ticket lists and in Needs you. An agent keeps it off by sending a heartbeat while it works. An open wait on you does not count as stalled.