Den is a DZone Zone Leader and has posted 460 posts at DZone. You can read more from them at their website. View Full User Profile

How do you track your bugs & issues?

03.05.2012
| 4253 views |

Software bugs are inevitable. Even with the most polished products, there are scenarios that cannot be predicted by the developer and the testers. Those depend both on software and hardware configurations, as well as user habits. That being said, for proper actions to be taken, bugs and issues should be tracked. There are many ways that process can be streamlined, including using pre-built systems that integrate issue tracking as a part of the project control - for example, CodePlex or GitHub. One of the issues with public outlets like these (although GitHub offers a paid service too) is the fact that all issues are available to the general public, which might not be the best choice for projects that might have critical vulnerabilities that can have a negative en-masse effect if publicly disclosed. The developer can also self-host a bug management solution, like BugZilla, or choose to use a subscription-based service like FogBugz. There are also cases when developers don't use any of these, TODOs in code being the only bug-tracking system - a horrible way to approach the problem by creating another problem, but as funny as it sounds, I've seen it happening.

Personally, all bug tracking for my projects is managed through the services those are hosted on. For example, most of my open-source projects are hosted on CodePlex and I really enjoy the simplicity of their issue tracking page. Users can easily create work items and I can later on prioritize and edit them. What's even more important, it is easy for me to track what features or issues deserve higher priority based on individual votes. For private projects, I once again use well-tested solutions that are well-integrated with the source control system (e.g. Assembla).

So what is your favorite solution?

Combined solutions (source control + issue tracker -> e.g. BitBucket, GitHub, CodePlex)
26% (41 votes)
Standalone solutions (e.g. BugZilla) - self-hosted
34% (53 votes)
Standalone solutions (e.g. BugZilla) - not self-hosted
1% (2 votes)
Subscription services (e.g. FogBugz)
2% (3 votes)
In-house (self-developed) systems
11% (17 votes)
Excel spreadsheet & other very basic methods
14% (22 votes)
Other (please specify)
12% (19 votes)
Total votes: 157

Comments

Ajya Chang replied on Mon, 2012/03/05 - 6:04am

Hello,

Thanks for article. Here I would like to say that we use our own bug tracking system that built for our own purposes. We have taken inspiration form jeera. Even the suggested softwares or tools are good. But there should be some tracking mechanism to track the system bugs. Even TFS can be used for the purpose of bugs maintainence and tracking.

Thanks

Alex Duderino replied on Tue, 2012/03/06 - 3:41pm

We're using Redmine and it rocks. Extremely flexible yet easy to use, even for our clients.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.