Reopen Surge Detector(3.1.8)

A stable reopen count, even a high one, is manageable. A reopen count that is growing week over week moves before sprint metrics do, because a reopen is recorded when work comes back rather than when it is next planned. This detector measures the acceleration of reopens — not just the count — so you can act before the trend becomes a crisis.

A project that doubled its reopen rate in two weeks needs a different response than one that has had a steady 15% rate for months. This visual shows you the trajectory, not just the position.

What you can conclude

• A week-over-week increase of more than 50% in any project is a high-priority signal — something changed in that project's process or scope that needs to be understood.
• Multiple projects accelerating simultaneously may indicate a systemic issue (a recent deployment, a process change) rather than project-level failures.
• A project where the rate is stable, even if elevated, is under control — the problem is known and bounded.

How this chart works

Multi-series line chart of reopens per calendar week, one line per project. Each point is the number of reopens recorded in that week, a reopen being a status change from a done status back to one that is not done. Each complete week is also rated against the week before it from the percentage change in that count, not from the absolute count: surge when the count rose by more than 50 percent, increasing above 10 percent, decelerating when it fell, stable otherwise. A week whose previous week had no reopens is not rated, because there is no base for a percentage. The rating is not drawn on the chart; it is published beside each week's count and is available to Deep Analysis.

The week in progress is shown at its raw count so far. Because the week is not yet complete, it carries no week-over-week change. It is not rated while it is open.