Issue Structure
Every issue has:Issue Types
| Type | Use Case |
|---|---|
bug | Something broken that needs fixing |
feature | New functionality |
task | Work item (tests, docs, refactoring) |
epic | Large feature with subtasks |
chore | Maintenance (dependencies, tooling) |
Priorities
| Priority | Level | Examples |
|---|---|---|
| 0 | Critical | Security, data loss, broken builds |
| 1 | High | Major features, important bugs |
| 2 | Medium | Nice-to-have features, minor bugs |
| 3 | Low | Polish, optimization |
| 4 | Backlog | Future ideas |
Creating Issues
Dependencies
Blocking Dependencies
Theblocks relationship affects the ready queue:
Structural Relationships
These don’t affect the ready queue:Dependency Types
| Type | Description | Ready Queue Impact |
|---|---|---|
blocks | Hard dependency | Yes - blocked items not ready |
parent-child | Epic/subtask hierarchy | No |
discovered-from | Tracks origin of discovery | No |
related | Soft relationship | No |