What is your favorite bug / problem tracking system? And why?

What is your favorite bug / problem tracking system? And why?

(Please answer this question only if you have been using at least three different error tracking systems for quite some time.)

+4
source share
13 answers

FogBugz is actually great, as it is:

  • easy to use
  • intuitive
  • integrates well
  • functional
+10
source

Trac! It is so well integrated with SVN . We just like it.

+9
source

Jira gets my vote. It is flexible and fast and has good integration with source control. It also has subtasks, good categorization, and customizable workflows.

+7
source

We just looked at the rather laborious process of reviewing many (maybe ten?) Problem tracking systems to replace GForge , which was getting in our way more than help. We looked at free and commercial systems.

To be honest, I was disappointed with all of the systems we reviewed. There are many opportunities for improvement in this domain.

Many of them had poor interfaces ( OnTime , JIRA , Bugzilla ). As a rule, our engineers were fine with this, but it is important that our project managers, system integrators and customers present an interface that is clear and aesthetic.

I was surprised to find that there is very little support for nested sub-problems. In the software world, of course, very often you have to break down a task (problem or new function) into smaller components and assign them to different people. However, most systems could not do this - or could not do it well.

Some systems were very powerful and customizable, but practically required third-party extensions or plugins to make them useful. I really liked the flexibility of JIRA and Trac , but we would have to spend considerable time setting up the systems to make them pretty or more functional.

Naturally, these are not the only functions with which we were associated, but this post is already too long!

Of course, your requirements will differ from our requirements - I urge you to find out what you need and carefully study it.

FogBugz , JIRA and Trac were on our short list, and they all had great features. But in the end, they were beaten by a product that was previously unknown to me: VisionProject .

VisionProject is attractive and provides a good balance between powerful and easy to use. The only drawback that we see at the moment is that their new interface (starting with version v4.0) Ajax-y was a bit of a mistake. Nevertheless, we had several corrections overnight, and sometimes within a few hours, in their team responsible for the mental reaction.

We are still testing the system and, although not perfect, we compare it with other rivals.

+3
source

Redmine It:

  • Open source

  • Ajax enabled

  • Email Interface

  • SCM integration

  • Integrated wiki

  • Custom Trackers, Workflow, and Roles

  • RSS and Email Notifications

I used JIRA (too complicated), Bugzilla (too garbage) and FogBugz (too expensive), and I think Redmine is fantastic.

+3
source

Team Foundation Server , although it is a little more than just an error tracker.

+2
source

Trac or FogBugz look pretty good.

+1
source

We accepted Trac because:

  • This is pretty easy to install: if you follow the installation instructions exactly, it works, and this is not the usual situation!
  • It is extremely easy to use.
  • It is configured for one project (components, ticket types, severity, versions, ...)
  • Has a flexible / custom report section
  • Has a built-in wiki

But for us it has a big drawback: CVS support. But we accepted it because it is not necessary.

+1
source

We used Bugtracker.net for a while.

This is good and the price (free) is correct.

Some of my favorite features (from the site):

  • Sending and receiving email integrates with the tracker, so that the error email flow is tracked with an error.

  • Allows you to record incoming messages as errors. So, for example, an email from your client can automatically turn into an error / ticket to the tracker.

  • Allows you to attach files and screenshots to errors. There is even a special utility for capturing the screen [screenshot], which allows you to take a screenshot, annotate it and publish it as an error in just a few clicks. (inspired by Fogbugz)

  • Add your own fields.

  • Sign up for email notifications that tell you when an error has been added or changed. Or, change your settings to receive notification of errors you are worried about.

+1
source

I have a discussion links page just like this , where people compared the bug / release tracks nearby, and then made the choice of the one they like best. There is no single tracker that consistently wins these competitions.

Of the open source Trac ( Python ), Redmine ( Ruby ), Mantis ( PHP ), and my own BugTracker.NET ( C # ), everyone has their fans, but I think open source has a tendency to choose technology, and also Appendix. FogBugz and JIRA seem to be the most popular commercial ones.

+1
source

Main tracker

It is free, incredibly simple and convenient. Provides a flexible development cycle instead of bloating "customize everything to fit your development process."

+1
source

Bugzilla is not so bad.

Bugzilla is very adaptable to various situations. Notable applications currently include IT support queues, system administration deployment management, chip design and development problem tracking (both before and after manufacturing), and software and hardware error tracking for fixtures such as Red Hat, NASA, Linux-Mandrake and VA Systems. Combined with systems like CVS , Bonsai, or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution for configuration management and replication issues.

Bugzilla can significantly increase individual employee productivity and accountability by providing a documented workflow and positive feedback presentation. How many times do you wake up in the morning, remembering that you had to do something today, but you just canโ€™t remember? Put it in Bugzilla and you have a record of it from which you can extrapolate milestones, predict product versions for integration and follow the discussion path that led to critical decisions.

Ultimately, Bugzilla puts power in your hands to improve your value for your employer or business by providing a convenient framework for your natural attention to detail and a knowledge store is booming.

0
source

I like VersionOne (www.versionone.com). Itโ€™s good if you use one of the Agile processes (for example, Scrum). You can manage all your functions and tasks in addition to managing all defects. There is a specific defect life cycle, it has an accessible API, can be integrated with CVS, and there is an Outlook add-in. It has many things that can improve, but overall it is a good defect management system if you use flexible methods.

0
source

All Articles