This section contains a short list of questions that you should feel comfortable answering about your current bug tracking system:
How long does it take to enter a new bug? (More than a minute for a simple bug can seem like an awfully long time when you have do it over and over again.)
Can you find the definitions of the reports that you regularly run?
Can you make copies of these reports, edit the copies, or back up the definitions of the reports to somewhere outside the bug tracking system?
How are bugs expected to progress through different states? Is there a diagram of this anywhere that users of the bug tracking system can easily find?
How do you make sure that the correct people are aware of all changes to a bug?
If you wanted to reassign 20 bugs to someone, would you have to do this one bug at a time, or is there an easier way?
Can you change a comment field in a bug after the fact?
How do you create historical reports using your bug tracking system?
How do you add or remove values such as release names from a field?
How do you modify the definition of a bug?
When is the data in the bug tracking system backed up? When was the backup last tested by recovering it into a standby system?
How big an attachment is deemed reasonable to add to a bug? 100KB? 1MB? 10MB?
How regularly is your bug tracking system cleaned up?
How will you move your current data to your next bug tracking system?
Most importantly, does your current bug tracking system really help or hinder your project overall?