User guide

Daily work

What the configured workflow feels like from a team member's seat: the pages you open every day, the buttons on them, and the small rules that keep the board honest.

Work → project → item backlog, board, timeline, roadmap, iterations everything is one link away

The Work page: where every day starts

The Work tab is one screen across every organization you belong to, with two views. My work lists your items everywhere at once - filterable by project, status, type and due date, with a Needs my attention switch that answers the only question a Monday needs: work assigned to you that is still open, plus anything carrying unread activity you follow - terminal work never shows up there. Projects lists the projects themselves, and New project starts one. The Dashboard button at its top opens your primary organization's board of saved filters - pills switch it when you belong to several organizations - see Search, filters, and export.

Inside a project

A project page carries its discussion, watchers and collaborators, and opens onto five working views: Backlog, Board, Timeline, Iterations and Reports. Watch makes the project yours to follow; Copy link hands anyone a URL that resolves for everyone allowed to see it.

The backlog: ordering is the plan

The backlog shows the project's whole tree, parents over children, in drag-to-rank order - the position you leave a card in is the plan's priority. Filter it by status, type, priority, label, assignee and iteration (including the Unplanned backlog), then make that view yours with Save as my default: from then on the backlog opens "showing your saved filters", with one click to Show all. These preferences are personal - teammates' defaults never move yours. Export CSV takes the current filtered view with it, and New work item files straight into the top of the tree. A completed project hides both buttons behind a Reopen to add work item decision, because adding work to a closed project is a change of plan, not a keystroke.

The board: now

The board shows one column per workflow status, in the order your admins set, and moves are the same transition rules everywhere else: drag a card to a column it is allowed to enter, or use the status selector on the card itself. Moves the transition matrix blocks are disabled, not hidden, so the shape of the workflow stays visible; a retired status keeps its column (marked Retired) until its last card moves out. An iteration filter turns the board into the sprint view. To take a card for yourself, set its assignee to you and move it into your in-progress column - claiming work is exactly that, assign plus move, the same pair of moves your agents perform through the token API.

The timeline: when

The timeline draws the rows the backlog holds - one per work item, every parent above the subtree it owns, the same filters and saved defaults applied - as bars across the calendar. A bar is the item's start and end date; an item carrying only a due date is a marker on that day; an item with neither keeps its row and says No dates, because a schedule cannot be invented from an absence. Drag a bar to move it (an arrow key moves a day, plus Shift a week), take hold of an end to change just that end, and the pair is written in one step, recorded as one change, and repainted in every other tab you have open.

Two kinds of bar are not draggable, on purpose. A parent's bar is the span of its whole subtree - earliest start and latest end across every level below it, not merely the rows a filter happens to leave on screen - so it moves when the work below moves and never because a date was typed into the parent itself. And finished work keeps its dates as the record of the day it closed, which the workflow wrote for you; amending that is a deliberate act on the work item's own page, not a gesture on a chart. Arrows between bars are the project's blocks relations, and a dashed arrow means the calendar already contradicts the dependency: the blocked work is planned to begin before its blocker ends.

The organization roadmap: what ships across projects

The Dashboard page has a second tab, Roadmap: one row per project, drawn across a quarter ruler. A bar is that project's time-box (its Settings → Progress: Time-boxed schedule), and the filled part of a bar is work delivered, not time elapsed - so a project that is on schedule but half empty still reads as half empty, which is exactly what a plan review needs. Projects are grouped by their categories; anything without a time-box keeps a row in the Unscheduled lane instead of vanishing. A portfolio is a saved filter: pick one at the top of the page - or open a filter and press Roadmap portfolio - and only the projects that filter's work touches are drawn, always inside your own access, so two teammates can open one URL and see their own truth. Each row clicks through to that project's timeline with the portfolio's conditions carried over.

Iterations: the time-box

An iteration is a named, dated container inside one project: Create iteration takes a name, a goal, and start and end dates, and the iteration walks through Planned → Active → Completed. Work joins by setting the item's Iteration field; the backlog's iteration filter and the board's filter show what is committed versus unplanned. Completed iterations are where Reports get their burndown, velocity, throughput and cycle time.

The work item, end to end

Every field on the item page exists for a reason: the type decides where it may nest, the status moves only along allowed transitions, priority and labels are the organization's triage vocabulary (type a new label to invent it), assignee and iteration say who and when, start/due dates and story points feed the schedule and the reports. Around it:

  • Children and parents. Add children from the item itself (New child item); with Derive status from children switched on, the parent stops being hand-driven: it starts from its active children, stays in progress while some are finished and others remain open, completes when every child is terminal - and Reopen exists for the day a finished parent has to take a new child anyway. The parent row names the parent's status beside its reference, so you can see whether the item above is still moving without opening it; a top-level item's parent slot is Project root, which carries no work-item status.
  • Related work items. Link the real dependencies: pick a relationship (Blocks, Relates to, Duplicates, Causes, Solves), search the target "by reference, title, project, or key", and press Link work item. Direction matters where it should: A blocks B is not B blocks A. Related items must live in the same organization - the move preflight says so out loud when a cross-org move would break one. Every row carries the other item's status as a dot and a label, so a blocker that already shipped says so without a click.
  • Discussion. The thread on the item is a first-class conversation: markdown, @name mentions, attachments, drafts, edits with history. This is where a story gets argued about - and where an AI agent reports its progress.
  • Attachments. The Attachments panel keeps files on the record beside the discussion, with Download all for the whole set. Uploads are virus-scanned, and anything that does not come back clean is never served to anyone.
  • Delivery evidence. Commits and pull requests attached to the item show up as delivery links - see Integrations and AI agents.
  • Watch. The button flips between Watch work item and Watching. Watching adds you to the item's participants, so its discussion activity reaches your notifications even when you are neither assignee nor author - and the same mechanism works on projects.
  • Copy link. Every item carries a short reference (ENG-1) and a stable permalink of the shape /o/<org>/w/ENG-1/. Paste it anywhere; it resolves for everyone allowed to see the item, even after the item's own slug is renamed.

Keep going