What metrics should we track for our bug tracking process?

The one metric that matters
Mean time to close (MTTC): How long from report to fix on average. This is the only number that tells you if bugs are getting fixed or rotting. Track it weekly.
Useful supporting metrics
Bugs reported vs. bugs closed per week: If you're reporting more than you close, the backlog grows. Spotting this trend early matters.
High-severity bugs age: Track how long critical bugs sit open. If critical bugs wait weeks, your process isn't working.
Metrics to ignore
Total open bugs is meaningless—it depends on your definition of "done." Closure rate without severity weighting hides whether you're fixing important stuff. "Bugs per developer" tempts blame-shifting and encourages under-reporting.
How to use metrics
Show MTTC to leadership. Use it to identify bottlenecks. If a bug waits three weeks for assignment but closes in one day, assignment is slow. If it closes in 10 days, development is slow.
Track trends, not absolute numbers
One week with 30 open bugs means nothing. Six weeks trending from 20 open to 40 open means your process is breaking.
Review monthly, not daily
Daily fluctuations are noise. Weekly trends show reality.