Backward Transition Rate Over Time(5.1.5)

This visual shows how often tickets are moved out of a done status (e.g. Done, Closed) back into one that is not done. Each such step back records work that was reopened after it was marked done.

The chart compares the weekly volume of forward transitions, meaning every status change that starts from a status outside Jira's Done category, against backward transitions. It draws counts, not a rate, and marks no week as above or below a threshold. 5% is a reference value MetaFrazo sets, not a standard: the Avg backward rate card turns red when backward transitions are more than 5% of forward and backward transitions combined in the selected period.

What you can conclude

• If backward transitions stay above 5% of forward and backward transitions combined, week after week, the questions are what done means for this work and whether it is closed before it is finished.
• If backward transitions cluster in specific weeks or projects, a reviewer could ask what changed there, such as a release, a handover, or how requirements were written.
• A consistently low share shows that work marked done mostly stays done.

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 out of a status in Jira's Done category (such as Done, Closed or Resolved) into one outside it (such as In Progress). Hover over each bar to see the exact count.

The week in progress is shown at its count so far. Because the week is not yet complete, it covers only what has been recorded up to now and can only grow as the week closes. A week that falls only partly inside the selected date range is drawn and marked partial, so a short first week is visible as a short week rather than read as a fall. A week in which the events were measured and no backward transition was found draws a short bar rather than nothing, so a clean week reads as a result and not as a gap in the data.