Bugs
A bug records a defect or incident with enough detail for someone to triage, own, and fix it.
Create a bug
Select Write in the sidebar and choose a bug, or add one from the backlog. Bugs also arrive through triage, from connected trackers such as Jira, Linear, GitHub Issues, or GitLab, and from the REST API.
What a bug needs
| Field | Purpose |
|---|---|
| Title | Names the defect or incident. |
| Description | Holds the detail someone needs to understand the problem. |
| Status | Shows whether the bug is in intake, planned, in progress, blocked, in review, completed, or cancelled. |
| Priority | Helps route urgent or important repair work. |
| Owner and assignees | Show who is accountable and who is doing the repair work. |
| Teams | Decide where the bug appears for planning, standups, and updates. |
| Parent initiative | Connects the bug to larger planned work when the repair supports a roadmap item. |
| Reporter and reviewer | Appear for triage and review intake flows. |
| Taxonomy | Connects the bug to a customer, product area, skill, or goal when that affects routing or reporting. |
For spec-driven development, the bug is the repair spec. Put investigation notes, screenshots, logs, or failing links in the description or comments when they help someone fix it.
When the report is rough, select Enter writer mode on the bug. Writer Mode refines the title and description and keeps the bug's status, comments, and linked work.
Complete a bug
When you mark a bug completed, the same optional completed-task behavior applies as for initiatives. Captured Work explains how those closures appear in Recap and the Journal.
Work insights
Bug detail pages include an Insights section below the brief and above comments, scoped to the open bug and directly related completed work. It uses the same cards and empty state as the Insights tab described in Initiatives.
Synced bugs
Bugs from Jira, Linear, GitHub, or GitLab stay synchronized with the source tracker. Titles, descriptions, status, priority, and assignees may be editable inline depending on the integration and its mappings.
Bug priorities from connected issue trackers
| Priority | Meaning |
|---|---|
Critical | Highest severity work that needs immediate attention. |
Urgent | Time-sensitive work that should interrupt normal ordering. |
High | Important work that should be handled before the default queue. |
Medium | Normal priority work. |
Low | Useful work that can wait behind higher-impact items. |
Lowest | Low-impact work to keep visible without crowding current planning. |
Synced issues follow the visibility rules of the source app, so assume teammates with access to that tracker can inspect the issue there. Keep private follow-up work in private todos.
Triage Items covers accept, decline, and duplicate decisions for bugs that arrive through triage.