Issues

An issue is one piece of work. Each one belongs to a project and takes its key from that project, like RUN-42. Beyond the title and description, an issue carries the properties that make it easy to scan, filter, and delegate:

• Status — where the work sits in your workflow
• Priority and Type — how urgent it is and what kind of work it is
• Assignee — the person or agent responsible
• Labels — cross-project tags for organizing and filtering
• Due date, sub-issues, linked issues, comments, and an activity trail

Descriptions and comments are written in a rich editor and stored as Markdown, so they read cleanly whether a person or an agent wrote them.

Priority

Five levels, ordered the way you triage: No priority, Urgent, High, Medium, Low.

Type

Three kinds of work: Task, Feature, and Bug.

Status

Statuses are defined per workspace and shared across every project. Each status belongs to one of five categories that drive grouping and open/closed behavior:

Add, rename, recolor, reorder, and set a default status under Settings — see Workspace settings.

Press c anywhere, click New issue on the issues list or board, or use the command palette. A panel slides in to capture the work and set its properties: title, description, project, status, priority, type, assignee, labels, and due date.

Open any issue to edit it in place. The title is editable inline. The description is a full editor that auto-saves as you type, showing a saving indicator. In the right-hand Properties panel, status, priority, assignee, type, labels, and due date each save the moment you change them.

Issues are archived, not deleted — archiving hides an issue from lists and the board while keeping its history, and you can restore it later.

Break a larger issue into sub-issues. The parent shows a progress bar and a done count, so you can see how much of the work is complete at a glance. Add a brand-new sub-issue or attach an existing issue as a child, and detach it when scope changes.

Relate issues so dependencies and duplicates stay visible. Links are grouped by relation on the issue:

Mention another issue inside a description or comment with a wiki-style link — [[RUN-12]], or [[RUN-12|a friendly label]]. Runboard turns it into a live link and records a backlink on the other issue, so the Text links section shows both what this issue points to and what points back at it. This is lighter-weight than a formal relation and great for cross-referencing context.

Discuss work in the comment thread. Comments are Markdown, support emoji reactions, and appear in real time — including a typing indicator while someone is writing. Mention a teammate with @name to notify them.

The Activity timeline records every change — status moves, assignments, links, sub-issues, agent runs, and more — so the full story of an issue stays attached to it, no matter who or what made the change.

Add reusable typed fields that apply to every issue in the workspace — text, number, date, checkbox, or a single-select list. Use them for the dimensions your team tracks that aren't built in, like risk level or environment. Custom properties are searchable (see Views & search).