States & Detail
Every item tracks work through a lifecycle of states and can be labeled with a custom item type. You also gain a full detail page for editing, organizing, and linking any item.
Item States
Each item is in one of these states:
- Open — The default state for a newly created item.
- In Progress — Work has started on the item.
- In Review — The item is awaiting review.
- Blocked — The item is blocked by another item or external factor.
- Resolved — The item has been addressed or fixed.
- Reopened — A previously resolved item has been reopened.
- Closed — The item is closed and no longer active.
- Stale — Marked automatically after inactivity (see Item Policies).
- Won't Fix — The item will not be addressed.
- Duplicate — The item is a duplicate of another item.
- Deferred — The item is postponed to a later time.
Item Types
Item types label an item beyond its state, such as Bug, Feature, or Task. Each repository defines its own set of types:
- Custom colors and icons — Each type has an optional color and icon.
- Default type — Repository owners can set which type is selected by default.
- Filtering — The item list can be filtered by type (and by state).
Item types are managed from the items list page. Type-related actions are gated by the item_types permissions.
The Item Detail Page
Opening an item shows a full detail page with the following:
- Title and description — The core content of the item.
- State and type — With permission to change both.
- Assignees — Members responsible for the item.
- Linked branches and change requests — See the Linking section.
- Dependencies — See the Linking section.
- Duplicates — See the Linking section.
- Discussions and notes — See the Discussions section.
- Pinning — Pin important items so they appear first in the list.
Creating Items from a Change Request or Branch
From an item you can create a branch, a change request, or both in one action. The platform
suggests a branch name based on the item (such as item/12-my-title) and can link
the new branch and change request back to the item automatically.
Permissions
Item operations are permission-controlled. Core permissions include item.items.create, item.items.read, item.items.edit, item.items.delete, item.items.close (for closing items), and item.items.pin. Fine-grained
permissions also cover types, assignees, threads, notes, dependencies, CR links, ref links,
duplicates, and policies. Anonymous and public access follow the repository's audience
permissions.