# Item Types and Fields

Nimbalyst ships seven built-in tracker item types, each with its own status workflow, fields, and icon. Learn what each type is meant to track.

Nimbalyst includes seven built-in tracker types. Each has its own status workflow, fields, and color-coded icon, so a bug moves through different stages than an idea, milestone, or plan. The type determines which columns appear on the kanban board and which fields are available in the detail view. If none of these fit a workflow, you can change them or add your own with [custom tracker types](https://nimbalyst.com/docs/task-management/custom-tracker-types/).

### Bug

For tracking defects and issues.

* **Icon:** Bug report (red)
* **Statuses:** To Do, In Progress, In Review, Changes Requested, Approved, Done, Won't Do, Duplicate
* **Fields:** Title, Status, Priority, Owner, Description, relationships, Tags

### Task

For general work items and to-dos.

* **Icon:** Task (blue)
* **Statuses:** To Do, In Progress, In Review, Changes Requested, Approved, Done, Won't Do, Duplicate
* **Fields:** Title, Status, Priority, Owner, Description, relationships, Tags

### Idea

For capturing ideas before they become work items.

* **Icon:** Lightbulb (yellow)
* **Statuses:** New, Considering, Accepted, Rejected
* **Fields:** Title, Status, relationships, Tags

### Decision

For recording architectural and product decisions with context.

* **Icon:** Gavel (purple)
* **Statuses:** To Decide, Evaluating, Decided, Implemented
* **Fields:** Title, Status, Chosen (the decision made), Priority, Owner, Stakeholders, relationships, Tags

### Plan

For larger initiatives with progress tracking.

* **Icon:** Flag (blue)
* **Statuses:** Draft, Ready, In Development, In Review, Changes Requested, Approved, Completed, Rejected, Blocked
* **Fields:** Title, Status, Plan Type, Priority, Progress (0-100%), Owner, Stakeholders, relationships, Tags, Start Date
* **Plan Types:** System Design, Feature, Bug Fix, Refactor, Documentation, Research

Plan items suit long-lived planning: write the goals, strategy, and architecture in the item's body, keep it updated as the work develops, and track progress on the item itself. Note this is different from Claude Code's `/plan` command, which creates a temporary plan for one implementation pass and is not integrated with the tracker. If you want conversational planning that lands in the tracker, create a custom slash command or skill (for example `/spec`) and have it create or update a Plan item.

### Milestone

For grouping work around a target date.

* **Icon:** Flag (purple)
* **Statuses:** Planned, Active, Done, Cancelled
* **Fields:** Title, Status, Owner, Start Date, Target Date, Description, Items, Tags

### Release

For grouping work into an alpha or stable release.

* **Icon:** Rocket (blue)
* **Statuses:** Planned, In Progress, Released, Cancelled
* **Fields:** Title, Status, Version, Git Tag, Channel, Released At, Owner, Description, Items, Tags

### Priority Levels

All item types that support priority use the same four-level scale:

| Priority | Use For                                       |
| -------- | --------------------------------------------- |
| Critical | Blocking issues that need immediate attention |
| High     | Important work that should be done soon       |
| Medium   | Standard priority (default)                   |
| Low      | Nice-to-have or can wait                      |