Page:
Custom-Statuses
Pages
Search wiki
Recent changes
t Print view
Export wiki (ZIP)
Branch-Protection-API
Custom-Fields
Custom-Statuses
Home
License-Management
MCP-Server
Metadata-API
Metadata-Settings
README
Security-API
Wiki-Folders
branding
deployment
issue-management
manifest-api
manifest-settings
roadmap
security-scanning
Clone
Contents
Table of Contents
Custom Issue Statuses
Org-defined workflow states with auto close/reopen.
Default Statuses
| Status | Color | Required |
|---|---|---|
| Open | green | Yes |
| In Progress | blue | No |
| Waiting | orange | No |
| In Review | purple | No |
| Closed | red | Yes |
| Won't Fix | gray | No |
Required Baseline
Open and Closed are required statuses (is_required=true) and cannot be deleted. They serve as the baseline workflow states. Custom statuses can be freely added and deleted on top of these.
UI Features
- Status dropdown in comment form (replaces close/reopen button)
- Lock icon and disabled delete button for required statuses
- "Required" badge on required status rows
- Colored badges in issue list view
API
GET /api/v1/orgs/{org}/issue_statuses-- list org statuses (includesis_requiredfield)- Issue create/update accepts
status_idparameter - The MCP server also supports the
status_idfield