Most-Reopened Issues Leaderboard

Some tickets just won't stay closed. They get reopened once, twice, sometimes more — each time representing additional unplanned work, delayed delivery, and accumulated frustration. This leaderboard surfaces those tickets directly so they can be prioritized for a root-cause conversation.

A ticket reopened twice is not just inconvenient — it is a signal that the underlying problem was not understood clearly enough the first time, or that the acceptance criteria weren't specific enough to prevent premature closure.

What you can conclude

• Tickets flagged as High risk (reopened 2 or more times) should be discussed in the next retrospective — what is preventing clean resolution?
• If multiple high-risk tickets belong to the same project or epic, the problem may be at the requirement or design level rather than execution.
• Use this list as a triage tool to prioritize technical debt or requirement clarification 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 tickets exist in the selected period, a green banner confirms the clean state.

Use the project and date filters to narrow the view. Suitable for use as a retrospective input or technical debt triage list.