Bug Tracking System

Bug tracking systems aim to provide full incident management, from logging the bug to assigning it to a developer to closing it out once its fixed. In Dev Force ONE, we refer to "bug tracking" as "incident tracking". The terminology "bug tracking" has a fairly negative connotation, and does not accurately describe cases where a "bug" is entered which is actually a feature request, optimization, ui change or even a tweak. For this reason, we use the terms "incident tracking" and "incident management" in Dev Force ONE. An incident is less conspicious and has a more neutral connotation; it's a generic term which encompasses all the different types of entries that could be made into the incident tracking sytem from bugs/defects to ui changes and tweaks. There are some bug tracking systems which use the terms "defect tracking" or "defect management", but again the connotation is overly negative and don't do neutral changes justice.

Unlike your typical bug tracking system, Dev Force ONE takes incident tracking to the next level by integrating it directly into a single Software Development Life Cycle solution - consisting of both project management and test case management systems. A "bug tracking system" cannot link a bug to a test suite, a test case or a test step - but with Dev Force ONE you can. Additionally, incidents can be submitted anonymously through customizable forms. These functionalities expand Dev Force ONE far beyond the limitations of a bug tracking system, and gives you the power and features you need to make your product stable and keep it that way. Plus, with our report system you can see a detailed view of all your projects, subprojects, test cases and incidents at any time.