Tickets & Kanban

Create structured work units, organize them visually, and track progress across your project.

Ticket Types, Priorities & Statuses

Every ticket has a type, a priority, and a status. These three properties control how work is categorized, sorted, and displayed on the board.

Types

Type	Color	Use for
Feature	Blue	New capabilities or user-facing functionality
Bug	Red	Defects and regressions to fix
Improvement	Green	Enhancements to existing features
Task	Yellow	General work items, chores, maintenance
Documentation	Purple	Docs, guides, and knowledge-base entries
Exploration	Cyan	Research, spikes, and investigation work

Priorities

Priority	Meaning
Critical	Blocking issue, fix immediately
High	Important, prioritize in current cycle
Medium	Standard priority (default)
Low	Nice to have, address when bandwidth allows

Statuses

Statuses map directly to Kanban columns. Moving a ticket between columns updates its status automatically.

Status	Column
Open	Backlog / To Do
In Progress	In Progress
In Review	In Review
Done	Done

Creating & Editing Tickets

Creating a ticket

Click the + button on any Kanban column, or use Cmd+N (macOS) / Ctrl+N (Windows).

Enter a title. Set type, priority, and any labels from the ticket inspector panel.

Write the description using Markdown in the built-in editor (see Markdown Descriptions below).

[Screenshot: Ticket inspector panel showing title, type, priority, and description fields]

Quick Capture

Press Cmd+G from anywhere in the app to capture a ticket with just a title. The ticket is created in the Open status with Medium priority. Refine it later by opening the inspector and filling in the remaining fields.

Tickets are stored in the database, not as files. They persist across sessions and are searchable from the Work Management view.

Editing a ticket

Click any ticket card on the board to open its inspector. All fields are inline-editable: title, type, priority, labels, and description. Changes are saved automatically.

Markdown Descriptions & Diagrams

Ticket descriptions support full Markdown with a live preview. The built-in editor includes syntax highlighting, headings, lists, tables, code blocks, and inline Mermaid diagrams.

[Screenshot: Markdown editor with headings, code block, and checklist]

[Screenshot: Rendered preview with Mermaid flowchart diagram]

Supported elements

Headings, bold, italic, strikethrough
Ordered and unordered lists, task checklists
Tables and horizontal rules
Fenced code blocks with syntax highlighting
Mermaid diagrams (flowchart, sequence, state, ER, etc.) — see Editor & Diagrams

AI agents can read and update ticket descriptions via the AIF Actions CLI, making descriptions a bridge between human intent and AI execution.

Kanban Board

The Kanban board is the default view for every project. Tickets are organized into columns that correspond to their status.

[Screenshot: Kanban board with four columns — Open, In Progress, In Review, Done]

Columns

The board has four fixed columns matching the ticket statuses: Open, In Progress, In Review, and Done. Each column header shows the count of tickets it contains.

Drag & Drop

Click and hold a ticket card, then drag it to another column. Dropping the card updates the ticket status immediately. You can also reorder tickets within a column by dragging them up or down.

Drag between columns to change status
Drag within a column to reorder
Ticket cards show type color, priority badge, and title at a glance

Dependencies & Parent-Child Relationships

Tickets can be linked in two ways: parent-child relationships for hierarchical decomposition, and dependencies for sequencing work.

Parent-child tickets

A parent ticket represents a large body of work. Child tickets (sub-tickets) break it into smaller, executable units. To create a sub-ticket, open a ticket's inspector and click Add Sub-ticket.

Parent tickets show a progress indicator based on completed sub-tickets
Sub-tickets inherit the parent's project scope
Each sub-ticket can have its own type, priority, and execution history

[Screenshot: Parent ticket with three sub-tickets showing progress indicator]

Dependencies

Dependencies express that one ticket must be completed before another can start. Add a dependency from the inspector's Dependencies section by searching for and selecting a blocking ticket.

Circular dependencies are detected and blocked. If ticket A depends on B, you cannot add A as a dependency of B.

Filtering & Bulk Operations

Filtering tickets

Use the filter bar above the Kanban board to narrow down visible tickets. Filters can be combined.

Filter	Description
Type	Show only tickets of a specific type (Feature, Bug, etc.)
Priority	Filter by priority level
Status	Show specific columns only
Label	Filter by assigned labels
Search	Free-text search across title and description

[Screenshot: Filter bar with type and priority dropdowns active]

Bulk operations

Select multiple tickets by holding Cmd (macOS) / Ctrl (Windows) and clicking ticket cards. Once selected, a bulk-action toolbar appears with the following operations:

Move — change status for all selected tickets at once
Set Priority — apply a priority to all selected tickets
Set Type — change the type for all selected tickets
Delete — remove selected tickets (requires confirmation)