Issue status

Set the statuses issues move through from backlog to done.

Set the statuses issues move through from start to completion.

Overview

Issue statuses define the type and order of states issues move through from start to completion. Every team uses the same workspace workflow:

Backlog → Todo → In Progress → QA → Release → Done.

Status types power charts and filters when you ask for Unstarted, Started, or Completed work, regardless of the column name:

  • Unstarted — Backlog, Todo
  • Started — In Progress, QA, Release
  • Completed — Done

Types Triage and Canceled exist for filters. Pulse has no issue status in those types. Incoming work that still needs a response lives in request triage.

Configure

Statuses are workspace-wide. You cannot add, rename, or reorder them. Every team uses the six statuses above.

Settings → Your teams → <team> → Issue statuses is the team settings card for status groups. It does not create custom columns.

Git automations that move issues live on Source control workflow, not Issue statuses. Personal coding tools can also Move the issue to In Progress from Settings → Code & reviews.

Change an issue's status:

  • Drag cards on the board
  • Press S on a selected issue, or use the status control on issue detail
  • Bulk-update selected issues with Change status…

An issue in an active cycle cannot be Backlog. An issue with open sub-issues cannot move to Done from issue detail. Release is only reachable from QA; from Release the next statuses are Done or QA.

Default status

New issues land in Backlog unless you pick another status in the composer or a template overrides it. Release is not a create option.

FAQ

Last updated on