Backward Transition Actor Ranking(5.1.6)

This visual shows which accounts move tickets backward most frequently, each labeled with the type Jira reports for it: a person, an app such as Automation for Jira, a service-desk customer, or unknown when Jira returned no type. A high count does not automatically indicate wrongdoing, but it marks someone as worth a closer look.

Backward transitions concentrate around specific people when there are unclear handovers, missing information at closure, or a workflow step that affects one part of the team more than others.

What you can conclude

• For actors with red bars (5 or more), a reviewer could ask what sent that work back out of done.
• A spread across many actors points to how the workflow is set up rather than to individuals.
• If the same actor appears here and in other compliance visuals, that is the strongest reason to read their transitions together.

How this chart works

Horizontal bar chart ranking the top actors by count of backward transitions they triggered, colored by deviation severity: red ≥ 5, orange 3–4, blue ≤ 2. Use the date and project filters to narrow the view to a specific period or team.