Work management
Views, filters and layouts
Filter once, then look at the same work as a board, a list, a table, a calendar or a timeline — and save the result.
A view is a set of filters plus how to draw them. The filters live in the URL, so a view is a link: paste it in chat and the person who opens it sees exactly what you were looking at. Getting around lists the addresses worth knowing.
One filter, every layout
Board, backlog, list, table, calendar and timeline all read through the same filter. There is deliberately no second implementation of what *my open bugs* means, because two implementations is how a list and a board come to show different work and neither is obviously wrong.
| Layout | What it is for | What it will not do |
|---|---|---|
| Board | Moving work between states. | — |
| Backlog | Ordering, and pulling into a sprint. | — |
| List | Reading quickly, and selecting in bulk. | — |
| Table | Comparing fields across many items. | Scrolls inside itself rather than making the page scroll sideways. |
| Calendar | Seeing what is due when. | Work with no due date is listed beneath the grid, never placed on a day it does not have. |
| Timeline | Seeing what overlaps. | Work with no dates is listed beneath, never drawn at an invented position. |
Nothing is drawn where the data does not say
A bar placed at a position nobody set is worse than an absent bar, because it will be believed. Calendar and timeline list undated work rather than guessing at it.
Grouping and swimlanes
Any view can be grouped by project, assignee, priority, type, state, initiative, release or label. On a board that draws swimlanes; on a list it draws sections. It is the same grouper either way, so a lane means the same thing wherever it appears.
The empty lane always comes last. Unassigned work and work with no release are exactly the rows people scan for, and burying them between two named lanes is how they stop being seen — but putting them first would push the ordinary work down the page every time.
Grouping by label is the exception: an item can carry several, so it appears in every lane it belongs to and the counts are marked as overlapping. The alternatives are both worse — picking a *first* label hides the others behind an ordering nobody chose, and a lane per combination produces forty lanes with one card each.
Saved views
A view can be saved by name, privately or shared with the organisation. Opening a saved view applies its filters and its layout; anything else in the URL still applies on top, so a shared view can be narrowed without saving a copy of it first.
A saved view naming something that has since been deleted still opens. The missing filters are dropped and the view says how many — one that silently returned nothing would look like a bug, and one that errored could not be repaired from the screen it broke on.