Backward Transitions

This visual shows how often tickets are moved from a terminal state (e.g. Done, Closed) back into an active status. Each such step back means a task was not fully completed the first time — this is measurable rework.

The chart compares the weekly volume of normal forward transitions against backward transitions. Weeks where the share of backward transitions exceeds the 5% compliance baseline are flagged for review.

What you can conclude

• If the rate stays above 5% consistently, it is worth reviewing processes, handovers, and how requirements are defined.
• If rework clusters around specific time periods or projects, this points to structural weaknesses or communication gaps.
• A consistently low rate indicates that tickets are closed cleanly and requirements were clear from the start.

How this chart works

Grouped bar chart showing the weekly volume of forward (blue) and backward (red) workflow transitions side by side. A backward transition moves an issue from a terminal state (Done, Closed, Resolved) back into an active state (e.g. In Progress). The compliance baseline is set at 5% — weeks exceeding this threshold are flagged for review. Hover over each bar to see the exact count.