Bug %
Work Mix & Quality Balance
%
Shows the percentage of completed work categorized as bugs or customer fixes.
💡 Like the ratio of repair work to new construction, some maintenance is healthy, but too much signals the foundations need attention.
What It Measures
Shows the percentage of completed work categorized as bugs or customer fixes.
Why It Matters
Understanding support load versus feature work
Monitoring quality issues and maintenance burden
How It's Calculated
Divides bug tickets by total tickets and multiplies by 100.
bug_tickets ÷ tickets × 100Concrete Example
If 6 of 20 completed tickets were bug fixes, your bug work is 30%, a high proportion that might indicate a quality or testing gap.
What Does a Healthy Score Look Like?
Lower is better, sustained high bug work signals quality issues.
Healthy
Under 15% of completed work
Watch Out
15–30% of completed work
Needs Attention
Over 30%, significant quality debt
What Moves This Metric?
Goes up when…
Accumulated technical debt surfacing as user-reported bugs
Recent releases introducing regressions
Insufficient test coverage allowing defects to reach production
Goes down when…
Stronger automated testing reducing defect escape rate
Better code review catching bugs before they ship
Dedicated bug-fix sprints clearing the backlog
Start Tracking Bug %
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com