Fast BugTrack vs. Alternatives

Manual Bug Tracking Processes

This bug tracking system usually revolves around a document, be it a whiteboard, a word-processing document, or a spreadsheet. The primary disadvantage of this system is that only a single person can update the document at once. This means that you must either dedicate a single individual to keeping the document up to date, or you must use the "baton" method, in which users pass the document from user to user, where the last person to be given the document can edit it, while others wait for their turn.

Disadvantages of this system:

The Homegrown Bug Tracking Solution

As a development team grows, the team will often assign a new / junior member of the team build a custom bug tracking solution. While this is an excellent way to teach a team member web programming, the development process, etc, it is probably not the best use of your organization's valuable resources. The system produced will likely track bugs very well, but will likely be missing critical features such as support for email notification or attachment support. This resource will end up devoting a considerable amount of their time maintaining / supporting their tool - this will quickly become an unrewarding task. While the initial tool might be very good, it was probably never designed with scalability in mind. Over time these issues begin to catch up with an organization, leaving them in a state in which their bugs are in an unmaintainable environment.

Disadvantages of this system:

Free Bug Tracking Systems

"Alcea Fast BugTrack was up and running in 5 minutes, and has saved us hundreds of dollars over trying to run and maintain a free bug tracking system. Its the smart way to go."
-- Cameron Elliott, Spamarrest LLC

Numerous bug tracking systems are available that are completely free. These systems are used on very large projects, scale very well, and likely include the critical features that make up a robust bug tracking system. For a development organization that is willing to expend the resources to install and maintain a free bug tracking system, this is likely the route to go. While there is no formal organization to provide technical support, the open source community is often very helpful in solving various technical issues that might arise. All of this sounds very good. What's the catch? The problem is that these systems are often built on other technologies and frameworks that also must be installed and/or maintained. For example Bugzilla needs Apache, MySql, Perl, and a local SMTP server. A user who is familiar with Unix and/or is a system administrator should be able to install this system. Non-technical users, or users whose time is valuable to them, will need to look elsewhere for a robust solution. We at Alcea have frequently worked with very technical development teams -- who know that they should be using a real bug tracking solution -- but who have simply not had the time and/or resources to install a proper bug tracking system and instead have resorted to the manual process. Fast BugTrack is aimed at this group of users who need a bug tracking system up and running in 15 minutes -- not 3 days later.

Disadvantages:

Other Commercial Bug Tracking Systems

"I do love this product! Unlike many of the much more expensive systems I've worked with, that try to do too much, Alcea Fast BugTrack does one thing and doe s it better. Simple and intuitive, what's not to love?"
-- Ernest Gautier, Quality Assurance Engineer, Medical Broadcasting Company

Other commercial solutions break down into 3 categories:

Hosted bug tracking solutions

If you are comfortable depending on another organization to maintain/host your bug tracking solution.

Disadvantages:

Thick client / server solutions

Disadvantages:

Other Web-based solutions

Disadvantages:

Fast BugTrack Advantages