Tickets

A ticket is one unit of work: a title, an optional Markdown description, and the metadata that helps you track it — column, tags, assignee, comments, and a full change history.

Creating and editing

Press C on a board or backlog to create a ticket, or use the add button in any column. Click a ticket (or focus it and press Enter) to open the detail view, which fills the board pane.

The description editor works in two modes, switchable from its toolbar:

• Rich mode — formatted text editing; what you see is what is stored as Markdown.
• Code mode — raw Markdown with syntax highlighting.

Both modes store plain GitHub-flavored Markdown: headings, lists, task lists, tables, fenced code blocks, links, and emoji shortcodes like :rocket:.

Ticket keys and references

Every ticket has a key like LAUN-42 — the board key plus a number that counts up from 1. Type a ticket key anywhere in a description or comment and Can turns it into a link to that ticket automatically.

⌘ + . / Ctrl + . copies the focused ticket's key; ⌘ + Shift + , / Ctrl + Shift + , copies its URL.

Tags

Tags are per-board labels with a name and a color. A ticket can carry up to 10 tags; a board can define up to 50. Add or remove tags from the ticket detail view (or press L), and create a new tag inline by typing a name that does not exist yet.

Assignees

A ticket has two assignee slots:

• Assignee — a workspace member, picked from the avatar in the ticket header (or press A; press I to assign yourself).
• Agent — an AI agent working the ticket via the API or MCP, shown with the agent's glyph on the card. See Hosted MCP server.

Comments

Each ticket has a comment thread with one level of replies. Submit with ⌘ + Enter / Ctrl + Enter, or focus the composer with Ctrl + M. You can edit your own comments; deleting one leaves a "deleted" placeholder so replies underneath keep their context. Comment bodies support the same Markdown as descriptions, including ticket-key autolinks.

Activity history

Every change to a ticket — title, description, status, assignee, tags — is recorded with the old value, the new value, who made the change, and when. Open the history section on the ticket detail view to walk back through it. Changes made through the REST API or an MCP agent are labeled with the integration that made them.

Backlog and status

A ticket lives either in a column or in the board's backlog. Press S (or drag) to move it between columns, into the backlog, or out of it. Moving a ticket to a different column updates its status timestamp, which the board can use to fade out tickets that have been done for a while.

Deleting

Press ⌘ + Backspace / Ctrl + Backspace (or use the detail view's menu) to delete a ticket. Deleting is permanent and removes the ticket's comments and history with it.