Self-Chain Detection

This visual surfaces tickets where one single actor drove every state change from start to finish — no colleague touched the workflow at any point. On its own, this is not always a problem. But in combination with a high hop count or a very short time span, it becomes a meaningful compliance signal.

In well-governed teams, workflow state changes on the same ticket are typically distributed across multiple people — someone picks it up, someone else reviews it, someone closes it. When all of that is done by one person, the separation of duties that compliance frameworks rely on is absent.

What you can conclude

• A high hop count with a short time span (minutes) is the most critical pattern — it suggests rapid, unreviewed state manipulation by a single actor.
• Actors who appear repeatedly in this log across multiple weeks or issues should be flagged for review.
• An empty log means all tickets had at least two distinct actors involved in their state history — a healthy sign.

How this chart works

Tabular log of issues where all status-transition events in a given week were triggered by the same single actor, with 2 or more transitions recorded. Columns: actor, issue key, hop count, time span (minutes between first and last transition), risk label. Distinct from the Missing Approval report — this log checks that the same actor drove every state change.