My organisation uses PVCS Tracker, mostly because it's easy to start using. We have relatively few specialist testers (just disgruntled, misplaced developers), so sophisticated software becomes shelfware and we have to rely on the humans. I leave the results to your imagination.

A lot of the above comments about developers hating bug tracking systems touch on one major aspect: the conflict between developers and testers. The people who have said that hating the bug tracking system is a proxy for hating the testers are onto something. But that's part of the job, sadly. As a tester, I have to proceed on the basis that there are bugs and my job is to find them. Any other mindset leads to failure and buggy code.

Of course, the really good developers are the ones who love their work, so a tester's mindset is not popular. As one of my colleagues said once, it's like having to tell you that your baby is ugly. Naturally, the systems that I use to tell developers their baby is ugly are going to be unpopular, however specifically they describe and track the ugliness.

In other words, there will never be a bug tracking system that's popular with its users. Perhaps that factor shouldn't be part of an evaluation of the systems in question.