Status Category Drift

A status name in Jira belongs to exactly one of three categories: To Do, In Progress, or Done. The category is what JQL statusCategory = … queries, automations, and category-pivoted reports (cycle-time, cumulative-flow, executive rollups) key on. This visual lists every status name in your tenant that maps to more than one category across the workflows we have seen — a silent drift signal that breaks every downstream consumer of the category field.

What you can conclude

• Any row is bad. The expected state is an empty table — every status name should belong to one category. A populated table means at least one workflow disagrees with another about what a status means.
• The category badges show the contradiction. If Ready for review shows both In Progress and To Do, JQL statusCategory = "In Progress" returns roughly half the matching issues, depending on which workflow created the issue.
• Severity scales with the badge count. A status mapping to all three categories is the worst case — every category-based query touching it is partly wrong.
• Remediation paths. Either rename the divergent statuses so the categories line up with the intent, or update the affected workflows to use a single canonical status with one category. Renaming is usually safer because it leaves automations and reports alone.
• Investigate it. Expand any row's per-project breakdown to see which project maps the name to which category (with event counts and a link straight to that project's workflow), or open the companion Status Category Drift Matrix for a status-by-project grid of the assigned categories.