The day view
One day of your workspace, in the order it happened, with the links between what caused what. It answers "what actually went on yesterday" without reading four screens and reconstructing the order yourself.
It is part of the work graph, and reachable from it. The map reads the workspace by connection; the day view reads it by time.
Three lanes
The day is drawn in three lanes, so you can see a handover between them rather than a flat list:
- People: tasks and comments, the things a person did.
- Run: agent runs, the steps inside them, and the waits while a run needed an answer.
- Code: pull requests, approvals, merges, alerts and reverts, and the waits while a pull request needed review.
You can show any combination. A day filtered to the run lane alone is a readable account of what the agents did; all three together show where the work passed from a person to an agent and back.
Picking a day
Choose the date, and the timezone it should be read in. The same day looks different from Helsinki and from San Francisco, and the view is explicit about which one you asked for rather than guessing.
You can also narrow the whole view to a single run, by its short id, which turns the day into that one run's story with the people and code events that touched it.
It is derived, never stored
The day view is worked out when you open it, from the records that already exist: the tasks, the delegation events, the runs and their steps, the pull requests, the approvals and merges, the alerts, the reverts and the waits.
Nothing is written when you read it. That matters more than it sounds: there is no second copy of the day to drift out of step with the records it came from. What you see is the same data the task and the run pages are showing, arranged by time instead of by object.
You see your own day
The view only ever shows records you could already open. Two people on different projects open the same date and see different days, and neither is missing anything they were entitled to.
The links between records follow the same rule. An edge is only drawn when both ends are records you can see, so a visible event never points at something you cannot open.
On the Free plan
Free keeps a 30-day run record, so a day view further back than that shows the people and code lanes but not the runs.
It says so rather than quietly showing less: the view reports how many runs the day held and how many it is showing you, so a short day reads as a plan limit rather than as a quiet morning. See Plans and limits.
Troubleshooting
| What you see | What it means |
|---|---|
| The run lane is empty on an older day | Free keeps 30 days of run record. The count tells you how many runs are not shown. |
| The same date looks different to a colleague | You see the projects you can see. Theirs are not the same projects. |
| An event has no link to the thing it obviously caused | One end is a record you cannot open, so the link is not drawn. |
| The day looks shifted by hours | Check the timezone. The view reads the day in the zone you picked, not the server's. |
Related
- Tasks and pull requests: the states the run lane moves through.
- Plans and limits: how long the run record is kept.
- The work graph: the same records read by what connects them.