Status Category Drift Matrix(5.10.8)

The flat Status Category Drift list answers "which statuses are in conflict?". This matrix answers the follow-up question: which workflow says what? Rows are the display names carried by two or more different statuses that do not all sit in the same category; columns are the projects that use them; each cell is the status category (To Do, In Progress, or Done) that project's workflow assigns, with one badge per category seen in that project.

What this matrix covers, and what it does not

The list above reports two kinds of finding. Only one of them is plotted here.

• Name collision — plotted. Two or more different statuses carry one display name and do not all sit in the same category. The row then reads "this label resolves to this category in this project" across the columns, which is the comparison that shows where the workflows differ. This is the case where statusCategory = "Done" in JQL returns one project's issues and silently omits another's.
• Category change — listed above, not plotted here. That finding is one status disagreeing with itself over time rather than across projects, so a matrix cell cannot carry it without changing what a cell means. Read those rows in the table above.

Because of that scope the matrix can be empty while the table above is not, which simply means every current finding is a category change. The panel says so rather than reporting no data.

How to read it

• A row with two or more colors is the disagreement — the same label resolving to different categories in different projects.
• A uniform row is consistent. Every project maps the label to the same category, so nothing is in conflict there.
• An empty matrix under an empty table is a measured answer, not a failed load: no finding of either kind was observed.
• Cells link to the source. Click a cell to open that exact project's workflow configuration in Jira, where the mapping is set.

How rows are identified

Statuses are identified by their Jira status id, so a status that was renamed is still one status and the label shown is its most recently observed name. A collision is keyed on the set of statuses sharing the label, so one collision seen under an old and a current label forms a single row rather than two. Statuses that share a label but agree on category do not form a row.

Before acting on a row. Which category a status is meant to have is your organization's decision; the matrix shows where projects disagree, not which side is intended. The per-project drill-down on the list above shows the event counts behind each mapping.