I once spent 2 weeks solving 4 related weird crashes that everyone complained about. Involved rewriting code that when I was finished removed 4,514 lines of code and never crashed again. I had my annual review 2 weeks later and the scoreboard was brought up. I told my boss I should get paid more for removing 4,514 lines of spaghetti from the software that made the "company nut". He laughed at me. 3 days later the CEO came down, personally thanked me as they were flooded with client happiness and took me to lunch. Some ear bending and casual talk about vision...next day the scoreboard was taken down and I was in charge of "core" functionality.
http://www.folklore.org/StoryView.py?story=Negative_2000_Lin...
Edit: actually, bug scoreboards need to die in a fire. But until then... they need two columns. :)
1. Did you really understand the bug you were fixing?
2. Did you test it at all?
3. Really did you test it?