Reopen Rate by Project(2.3.6)

Not all projects reopen tickets at the same rate. Some teams close work cleanly—once is enough. Others cycle tickets through Done and back repeatedly. This visual shows you the cross-project comparison so you can see where rework is concentrated.

A high reopen rate in a specific project is often a sign of thin acceptance criteria, unclear requirements, or a missing testing gate—not individual failure. It is the starting point for a targeted process conversation with that team.

What you can conclude

• Projects with a reopen rate above 15-20% are worth a direct process review—something in their definition of done is not holding.
• A project at 0.0% is a MEASURED zero, not an absence of data: it recorded completions in this window and no reopens. It may be genuinely clean, or it may be closing tickets that were never really finished—worth a spot check either way.
• A large gap between projects on the same team suggests process consistency issues rather than individual skill differences.

How this chart works

Both sides of the ratio are counted on the same days. For each project the chart sums the completions recorded on every day inside your selected window, sums the reopens recorded on those same days, and divides. Widening or narrowing the date range moves both numbers together, so the rate stays comparable across ranges.

A project that recorded reopens in the window but no completions has no denominator, so its rate cannot be computed and it is left off the bar chart rather than drawn at zero—an undrawn bar and a 0.0% bar mean different things here.

Because a reopen refers to a ticket completed on an earlier day, a project's rate can exceed 100% over a short window. That is arithmetic, not an error, and it is a signal the window is too narrow to read as a rate.

Projects are ordered by reopen rate descending. Use the project and date filters to narrow the comparison.