Reopen Rate by Project

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 immediately see where rework is concentrated.

A high reopen rate in a specific project is often a sign of poor acceptance criteria, unclear requirements, or missing testing gates — not necessarily 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 working.
• Projects with 0% reopen rate may be genuinely clean, or may be closing tickets that were never actually completed — worth a spot check.
• A large gap between projects on the same team suggests process consistency issues rather than individual skill differences.

How this chart works

Horizontal bar chart ranking each project by its reopen rate (%). Each bar shows total completions and total reopens side by side.

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