Bugs Assigned %
Delivery Throughput
%
Shows the percentage of your assigned tasks that are bugs.
💡 Like checking how much of your day is spent fixing mistakes versus building new things, a window into quality debt.
What It Measures
Shows the percentage of your assigned tasks that are bugs.
Why It Matters
Understanding your bug-fix workload balance
Monitoring if you are disproportionately assigned bug work
How It's Calculated
Divides bug tasks assigned by total tasks assigned and multiplies by 100.
100 × COUNT(assigned_bugs) ÷ COUNT(assigned_tasks)Concrete Example
If 6 of your 20 assigned tasks are bugs, your bug assignment rate is 30%, meaning nearly a third of your work is reactive fixes.
What Does a Healthy Score Look Like?
Lower is better, high bug load signals quality or planning issues.
Healthy
Under 15% of assigned tasks are bugs
Watch Out
15–30% of assigned tasks are bugs
Needs Attention
Over 30%, significant quality or tech debt issues
What Moves This Metric?
Goes up when…
Product quality issues driving more bug reports
Specialised bug-fix role or rotation
Recent release causing a wave of customer-reported issues
Goes down when…
Stronger testing and QA practices reducing defect rates
More investment in code review catching bugs before they ship
Shift toward new feature work after a quality improvement sprint
Start Tracking Bugs Assigned %
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