bug tracking : Java Glossary

bug tracking
When you have a large project you need some sort of database to keep track of bugs, who is assigned to fix them, have they been fixed, have the fixes been verified. A more general system tracks all manner of tasks in getting a project ready.

Most of them let you take them for a test drive. That’s the best way to get one that’s the right fit for you.

Programmers tend to hate task trackers and will rebel if you force them to encode too much detail. Err on the side of making the programmers enter too little detail. Keep your codes simple so that programmers don’t waste time trying to find the right or waste time haveing someone recode entries with the wrong code. Navigation is the big problem: finding a piece of information if you don’t know its code.

Bug trackers include Bugzero and Bugzilla.

Task trackers include Jira, Edgewall Trac and RT: Request tracker.


CMP homejump to top You can get the freshest copy of this page from: or possibly from your local J: drive (Java virtual drive/mindprod.com website mirror)
http://mindprod.com/jgloss/bugtracking.html J:\mindprod\jgloss\bugtracking.html
logofeedback Please email your feedback for publication, letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : feedback email If you want your message kept confidential, not considered for posting, please explicitly specify that.
mindprod.com IP:[65.110.21.43]
view BlogYour face IP:[38.107.179.213]
You are visitor number 6,972.