Boards, lanes, and tickets

The work hierarchy is:

Workspace → Project → Board → Lane → Ticket

A board is a flexible container, not a prescribed sprint or kanban process. Use separate boards for a roadmap, operational flow, product area, release, or any boundary that helps the team.

Choose a board color when you create or edit a board. The project sidebar uses that color on the board icon. Kanban and Table views show the same color beside each board title. Board names stay readable in light and dark themes.

Lanes group tickets and can be reordered, archived, and restored. A lane may also apply entry actions when a ticket enters it—for example setting status, priority, ticket type, assignee, requesting a review, or archiving the ticket. The destination lane's configured actions are authoritative. Reordering within the same lane does not rerun them.

Tickets hold title, description, kind, status, priority, due date, assignees, comments, watchers, attachments, Replay, checklists, typed attributes, reviews, time, blockers, and linked Context. Kinds include Ticket, Feature, Epic, Bug, Research, and Action Item.

Boards offer Kanban and Table layouts. Kanban supports visible ordering and drag-and-drop. Table supports sorting and comparison across the current board or lane without changing saved ticket positions. Filters for status, assignee, priority, and reporter apply to both layouts.

Boards can be archived and restored without deleting their lanes, tickets, comments, or history.

The project sidebar shows the first ten active boards. Select Show all boards (total) to expand the list and reveal Search boards. Search checks every active board by name. Select Show fewer to return to the compact list. Your current board stays visible even when it is outside the first ten or does not match the search.

The sidebar remembers expansion separately for each project in this browser. Search text is cleared when you collapse the list or change projects. Projects with ten or fewer active boards do not show these controls. Archived boards stay outside sidebar navigation.

Tickets may have a parent on the same board. Parent relationships show grouping and progress but do not automatically complete or archive children. A ticket can also be blocked by one active ticket in the same project; cycles are rejected and completed blockers display as resolved context.

Moving a ticket across boards is deliberate and stays within the same project. Parent/child relationships that would cross the board boundary must be cleared first. Cross-project moves are not supported.