Most-Reopened Issues Leaderboard(2.3.8)

Some tickets do not stay closed. They are reopened once, twice, sometimes more, and each reopen brings the ticket back into open work. This leaderboard lists those tickets directly, so you can see which ones keep coming back.

A ticket reopened twice came back out of a done status twice; the events show that it returned, not whether the problem was misunderstood, the acceptance criteria were loose, or the work itself changed.

What you can conclude

• A ticket flagged as High risk (reopened 2 or more times) has come back at least twice; a reviewer could ask what is preventing a clean resolution.
• If multiple high-risk tickets belong to the same project, the reopens are concentrated there rather than spread across the portfolio; the events do not say whether requirements, design or execution explain them.
• Read the list as the tickets whose closures did not hold, not as a ranking of anyone's work.

How this chart works

Ranked table of issues with the highest reopen count, including project name, issue key, full issue summary, reopen count, and a computed risk badge: High (≥ 2 reopens) or Low (1 reopen). High-risk rows are highlighted in coral for immediate visibility. When no high-risk ticket is listed, a green banner confirms the clean state. The reopen count and the risk badge cover a ticket's whole history; the date filter selects which tickets are listed, not the span they are counted over.

Use the project and date filters to narrow the view.