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.

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, or archive state. 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, assignee, comments, watchers, attachments, time, blockers, and linked Context. Kinds include Ticket, Feature, Epic, Bug, Research, and Action Item.

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.