Tickets & Kanban

Tickets are Quazzar’s built-in work tracker. Every ticket is a small card with a title, body, assignee, priority, and state. Cards live on a Kanban board you can drag between columns, and they can be linked to Molly memories and Notes so AI context flows naturally into your work.

Open Tickets & Kanban from the dock’s Work group in Personal mode, with g t, or with Ctrl/⌘+K. Deleting a project asks for confirmation. Single-user ticket workflows are free on every plan.

Ticket lifecycle

Tickets move through four states:

State	Meaning
Open	Newly created, not yet scheduled.
In progress	Someone is actively working on it.
Review	Work is done, waiting for sign-off or merge.
Done	Closed. Drops off the default Kanban view.

State transitions are free-form. Drag a card between Kanban columns, click the state chip in the detail view, or call the API.

Creating a ticket

Click New ticket on the Tickets page (or press N on the Kanban board). Fill in:

Title — short description.
Body — Markdown supported. [[Wiki-links]] to notes resolve, #tags are parsed, code fences render.
Assignee — pick from the user list. Leaving it empty creates an unassigned card.
Priority — low, normal, high, urgent. Priority drives the default sort on the Tickets page.
Labels — freeform text, comma-separated. Labels are searchable across the page.
Linked notes — attach one or more notes by title. The notes’ wiki-link back-reference lights up so you can trace work from context.

Kanban board

The Kanban view is four columns (Open / In progress / Review / Done) with a draggable card per ticket. Features:

Drag a card to a new column to change state.
Drag a card up or down within a column to reorder (persisted per user).
Click a card to open its detail drawer without leaving the board.
The column header shows the current count and aggregate priority.

Filtering

Use the filter bar above the board:

Assignee — my tickets / specific user / unassigned.
Priority — one or more priorities.
Label — multi-select.
Namespace — if your tickets are partitioned by project.

Every filter updates the URL so the view is shareable.

Linking from Molly memories and Notes

Any note or memory can reference a ticket by its id using standard wiki-link syntax:


Still open: [[ticket:TKT-128]]

Clicking the link opens the ticket in a side drawer. The ticket’s Linked from panel lists every note and memory that references it, so an AI that remembered a deployment issue surfaces the right ticket the next day.

Molly’s /remember slash command picks up any [[ticket:...]] reference in the remembered text and stores it as a link on the memory row, so future memory_search calls can pivot on the ticket id.

Keyboard shortcuts

Shortcut	Action
`N`	New ticket (when board or list is focused)
`/`	Focus the search box
`J` / `K`	Next / previous card (list view)
`Arrow` keys	Move selection on Kanban board
`Enter`	Open the selected card
`Esc`	Close the detail drawer

API

Tickets are exposed under /api/tickets on the Cloud OS REST API. See Cloud OS API for the full surface. Common paths:

GET /api/tickets — list with filters.
POST /api/tickets — create.
GET /api/tickets/:id — detail.
PATCH /api/tickets/:id — partial update (state, priority, assignee).
DELETE /api/tickets/:id — archive (soft delete; ?hard=true removes the row).

Orbit Notes — wiki-link target for tickets
Molly Memory — pulls ticket context into chat
Memory MCP — external AI clients can write memories that link to tickets