Effective Bug Tracking Process
Bugs are part of every product development process. How do
you track the bugs you find during product development and after? Bugs that are
found but not properly tracked might slip away and be discovered by your
customers. To avoid this from happening, the testing and development team
should work together using a bug-tracking tool. The Bug Life Cycle Model (http://www.elementool.com/help/buglifecycle.html) explains how to efficiently use your bug-tracking
bugs, enhancements and features (AKA Issues) are submitted to the
bug-tracking tool by the testing team or product manager.
product manager or team leader sets priority and severity to each new
Issue and assigns the Issue to a specific programmer.
programmers fix the Issues that have been assigned to them. The fixed
Issues status is changed to Fixed in the bug-tracking tool.
releases a new internal version with the new features and fixed Issues.
testing team checks whether all Issues that have been marked as fixed are
testing team closes the Fixed Issues in the bug-tracking tool. New bugs
are submitted go back to No. 1.
What should you look for in a bug-tracking tool:
notifications whenever an Issue is assigned to a group member. It is
very useful that your bug-tracking tool would send an automatic email
notification informing the programmer that a new Issue has been assign to
attachments the ability to attach screen shots, text file etc. that
provide the other team member with a clear description and example about
the problem that has been reported.
Trail automatically tracks and displays all changed made in a specific
Issue from the moment that the Issue has been submitted throughout its
customization It is important that your bug-tracking tool enables you to
fully customize the different forms, which are used for submitting Issues,
according to your special needs.
reports a report engine that enables you to search your Issue list for
different words and phrases, create focused reports with only the Issues
that interest you (using AND/OR/NOT), set the fields that should be
included in your Report Query and set the fields that should be displayed
on you Issue Report.
- Submitting issues
directly from your website this option enables your customers or team
members to submit Issues to your bug-tracking tool using a form that is
placed on your website, without the need to login to the tool.
enables access to the tool and Issue list from different locations using
only a browser.
Setting Priority and Severity:
Priority: A priority classification of a
software error is based on the importance and urgency of resolving the error.
The priority classification is as follows:
The bug should be resolved immediately.
High - This bug should be resolved as soon as possible
in the normal course of development activity, before the software is
This bug should be repaired after serious bugs have been fixed.
It can be resolved in a future major system revision or not be resolved
Severity: A severity classification of a
software error is based on the degree of the error impact on the operation of
the system. The severity classification is as follows:
The bug causes a failure of the complete software system, subsystem or a
program within the system.
- The bug does not cause a failure, but causes the system to produce
incorrect, incomplete, inconsistent results or impairs the system
The bug does not cause a failure, does not impair usability, and does
not interfere in the fluent work of the system and programs.
The bug is an aesthetic, is an enhancement or is a result of
non-conformance to a standard.
- The leading Web-based Bug Tracking Tool