For a tester, reporting bugs and keeping track of them is as important as finding bugs. And hence Bug Reporting gains the highest priority in the QA Process. There are so many reasons and advantages for using a bug tracking tool such as increased productivity, having everyone in the project be aware of bug status and progression, formalized way of reporting bugs and so on. Though some individual organizations develop, use and maintain their own bug tracking tool, there are numerous open source bug tracking applications available in the market to use. It is vital for the QA management to decide which tool among them is best suited for its organizational processes.

1. Evaluating Bug Tracking Systems
For a tester, reporting bugs and keeping track of them is as important as finding bugs. And hence Bug
Reporting gains the highest priority in the QA Process. There are so many reasons and advantages for
using a bug tracking tool such as increased productivity, having everyone in the project be aware of bug
status and progression, formalized way of reporting bugs and so on. Though some individual
organizations develop, use and maintain their own bug tracking tool, there are numerous open source
bug tracking applications available in the market to use. It is vital for the QA management to decide which
tool among them is best suited for its organizational processes.
Here are some ideas on how to decide upon the most correct and appropriate bug tracking tool for your
organization.
A bug tracking system should be adaptable: If you decide that you want to track more than just
bugs like Testcase document, support calls and so on, you should be able to do so.
It should maintain change histories for bugs – if you want to track changes to bugs itself. An
example of this could be Team Leader changing the bug priority from Medium to High.
Bug tracking system should support customizable fields like allowing administrators to add new
fields for Bug reporting, or editing/renaming field name, field content(adding/deleting drop-down
items) and even sometime deleting/hiding unnecessary fields
Notifications supported by the Bug tracking System in form of Email, RSS feeds or in Twitter
Bug Tracking system should be easy to use with a minimal learning curve for users including non-
technical users, requiring few mouse clicks and containing user-friendly fields to enter for every
bug, and so on
Level of security required at
- Field-level permissions control whether users can edit, or even view, fields
- Bug-level permissions control access to bugs by users.
- Feature-level permissions control access to specific features, such as reporting
- Project-level permissions determine which users can access which
projects/databases.
And finally, Bug tracking systems should support the ability to generate reports, including
customized Reports
If anyone who can verify the above checklist items, they can easily finalize their Bug tracking tool
from the vast available collection, or even enhance their existing Bug tracking system effectively.
Visit IVESIA’S WEBSITE Follow us at LINKEDIN and TWITTER