> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/task-management/item-types-and-fields.md).

# 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](/task-management/custom-tracker-types.md).

### 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                      |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nimbalyst.com/task-management/item-types-and-fields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.