Work-Item Types

Work-Item Types make features usable as dev work items: every feature carries a Type (features.type_id → work_item_types) alongside its status. The catalog is workspace-scoped: each workspace defines its own taxonomy here.

Members, admins and owners can manage it; commenters and viewers see a Locked panel.

Defaults

Every workspace is seeded with three types (at provisioning, so they exist before the first feature):

• Feature: the default for new features; the only type flagged for the roadmap
• Bug
• Tech-Debt

Add more (Chore, Spike, Hotfix, …) with the Add type field.

What you can do per type

• Recolor: pick from the design-token palette (drives the tinted Type pill everywhere)
• Rename: the label is display-only; the key slug is stable and used by import/export matching
• Reorder: controls dropdown and settings ordering
• Make default: exactly one default per workspace; pre-selected on new features and used for rows with a NULL type_id
• Roadmap toggle: show_on_roadmap; only flagged types appear on the Roadmap page and on the public/embed roadmap (default: Feature only), so bugs and internal work stay off both, and never leak to customers. A feature with no type follows the default type's toggle on the Roadmap page; the public roadmap withholds it.
• Archive: soft-retire. Archived types stay resolvable on existing features but aren't offered for new ones; they're listed under Archived with a Restore action. The default type can't be archived; pick a new default first. There is intentionally no delete in the UI.

Where Type appears

• The Type column on /features (first enum column; filterable), the type select in the feature dialog header next to Status, and the table cell editor
• Sprint-board and roadmap cards, feature pill hover tooltips, and member-pill feature lists
• Import/export: the Features sheet's Type column (matched case-insensitively by label or key; unknown values fall back to the workspace default)
• API: type_id is writable/filterable on /api/v1/features; the catalog itself is CRUD-able at /api/v1/work-item-types
• AI: the copilot reads each feature's type and resolves type_id against this catalog when proposing changes

Related

• Features: status workflow + work-item fields (estimate/spent hours, lead)
• Import / export: Features sheet columns
• Custom fields: the other per-workspace taxonomy surface