Status Category Drift(5.10.7)

A status in Jira belongs to exactly one of three categories: To Do, In Progress, or Done. That category is what JQL statusCategory = … queries, automations, and category-pivoted reports (cycle-time, cumulative-flow, executive rollups) key on. Jira records the assignment on every status; nothing in its UI aggregates those assignments across workflows and across time, which is what this table does — over the last 12 months, in two kinds.

The two kinds of finding

• Name collision, badged Shared name on the panel — two or more different statuses carry the same display name, and across those statuses more than one category is observed. One label means two things depending on which workflow produced the issue.
• Category change, badged Changed category — one status, tracked by its Jira status id, whose own category moved during the window.

Every row says which kind it is. A status involved in both appears once per kind: that is two findings about one status, not one finding counted twice.

What you can conclude

• The category badges show the disagreement. On a name collision, statusCategory = "Done" in JQL returns one project's issues and silently omits another's, so the result looks complete and is not.
• Read the category count against the row's kind. On a name collision it counts categories spread across several different statuses; on a category change it counts one status's own history. They are not the same measurement and do not add together.
• An empty table is the expected, healthy state — neither kind was observed — not a table that failed to load.
• Remediation paths. Either rename the divergent statuses so the labels stop overlapping, or repoint the affected workflows onto a single shared status with one category. Renaming is usually safer because it leaves automations and historical reports alone.
• Investigate it. Expand a row's per-project breakdown to see which project maps it to which category, with event counts and a link straight to that project's workflow, or open the companion Status Category Drift Matrix, which plots the name collisions on a status-by-project grid.

How this table works

Statuses are identified by their Jira status id, so a status that was renamed is still one status and its category change survives the rename; the label shown is the most recently observed name. A name collision is keyed on the set of statuses sharing the label, so one collision seen under an old and a current name is a single row rather than two. Statuses that share a label but agree on category are not listed. Where an event carries no status id the label is used instead, so nothing goes uncounted; such a grain can only ever produce a category change.