Zero-Comment Closures by Project

When a ticket is closed without a single comment, it means no one documented their review, no peer left feedback, and no discussion was recorded. For low-stakes tasks this may be acceptable. For compliance-relevant work — bug fixes, access changes, policy updates — a zero-comment closure is a missing approval signal.

This visual shows you the rate of zero-comment closures per project so you can identify where approval discipline is weakest.

What you can conclude

• A project where more than 15% of closures have no comments has a systematic approval gap — not an isolated exception.
• Comparing zero-comment rates across projects reveals whether approval gaps are concentrated or portfolio-wide.
• A declining zero-comment rate over time indicates that review culture is improving.

How this chart works

Grouped bar chart showing zero-comment closures versus comment-present closures per project, with the zero-comment rate percentage annotated. Use the date and project filters to focus on specific periods.