docs/issue-management.mdx
Issues are the fundamental unit of work in Vibe Kanban. They represent a bug, feature, or piece of work to be done — and they become the prompt your coding agent receives when you create a workspace. This guide walks you through the full issue lifecycle.
You can create an issue from the + button on any column header, or from the New Issue button in the filter bar.
<Frame> </Frame>Use the Team and Personal tabs to switch between all project issues and only those assigned to you.
<Frame> </Frame>Give your issue a clear, specific title that describes the outcome you want. The issue panel opens on the right where you can fill in the details.
<Frame> </Frame>The description is where you provide context for your coding agent. Use the rich text editor to format your instructions with bold, italic, lists, and inline code. You can also use markdown shortcuts for headings (#) and links ([text](url)).
A good description makes the difference between an agent that delivers exactly what you need and one that goes off track.
| Element | Weak example | Strong example |
|---|---|---|
| Title | "Fix bug" | "Fix login timeout on slow connections" |
| Description | "It's broken" | "Users on 3G see a timeout after 5 s. Expected: graceful retry with exponential backoff." |
Use priority to signal urgency, assign the issue to a team member, and add tags to categorise your work.
<Frame> </Frame>| Priority | When to use |
|---|---|
| Urgent | Production is down or users are blocked |
| High | Important work that should be picked up next |
| Medium | Standard work in the current sprint |
| Low | Nice-to-have improvements or future ideas |
Drag and drop issues between columns to change their status, or within a column to reorder them.
<Frame> </Frame>| Column | What it means |
|---|---|
| To do | Work that hasn't started yet |
| In progress | An agent or person is actively working on this |
| In review | Work is done and waiting for your review |
| Done | Completed and verified |
The Backlog and Cancelled columns are hidden by default — switch to the All tab to see them.
<Frame> </Frame> <Tip> To reorder issues within a column, make sure sorting is set to **Manual**. Other sort modes (Priority, Created, Updated) override manual ordering. </Tip>Large features are easier to manage when you break them into smaller, agent-sized tasks. Sub-issues let you create parent/child relationships between issues.
To add a sub-issue, open the parent issue and scroll to the Sub-Issues section. You have two options: click the + button to create a new sub-issue, or click the link button to connect an existing issue as a child.
<Frame> </Frame>Key rules for sub-issues:
A workspace is where your coding agent does the actual work. Open an issue and scroll to the Workspaces section. You have two options: click the + button to create a new workspace, or click the link button to connect an existing one.
<Frame> </Frame> <Info> You can connect multiple workspaces to a single issue — useful for running agents in parallel on different parts of the same feature. </Info>