Bugzilla vs. RepoPro

For any organization that follows a SDLC (Software Development Life Cycle), Bugzilla is a great tool that will facilitate documenting and tracking software issues. Email reminders notify users in the workflow process of who needs to work take action or what the status of the bug is. Task leaders/managers can keep a tab on the overall status of the software bugs. It may not have the bells and whistles of other tools, but serves the purpose as is, out of the box.

Incentivized

• Project synchronization. Used as the primary resource for bug tracking, bugzilla can serve as a powerful project synchronization tool. Every aspect of the tickets can be tracked; status changes, comments, added watchers, who's currently working on the issue, and if it's related to another issue.
• Unlimited Space. I currently work with a company who services hundreds of clients - and bugzilla helped us manage each one.
• For companies with a need to service many different projects, or iterations of the same project, bugzilla handles this task exceptionally well.
• Workflow assignments. Workflow is customizable by the simply selection of a checkbox. If ever the workflow needs to be altered, doing so is as simple as a .2 second "click".

Incentivized

• User interface is terrible. It was built in the 90s and still looks like it. While the back-end is robust, the front-end is antiquated. It provides too many options and is easy to break.
• Reporting is weak. It provides some basic statistics but doesn't provide details. You can find out how many reopens there are, but you can't know how quickly things go from reopen to complete.
• Doesn't have the best "canned" workflows. Software is done by teams. Bugzilla doesn't "out of the box" have workflows that mimic what a typical software organization does.

Incentivized

For future projects I will look at something that is hosted in the cloud that I don't have to manage. I would also like something that has a more modern feel to allow my customers to use it as well as my employees.

Incentivized

This is a pretty straightforward system. You put in the bug details, a ticket is created, the team is notified. The user interface reflects this very simple and straightforward flow. It's certainly much easier than trying to track bugs with using Excel and email.

I used it.

Incentivized

No real issues here.

Since it is open source, it doesn't have customer service. However, the amount of information on forums is vast. If you can wade through it, you'll get what you need

Incentivized

I know it.

Incentivized

Implementation was pretty simple. Particularly because the product cannot be customized so there is not much to do apart from getting it up and running.

Bugzilla is affordable and easier to use by newly forming team or group in our organization. As the team grows bigger we still continued to use Bugzilla as it is comfortable to use. We tried JIRA tool for bugtracking but it was expensive when compared to Bugzilla so switched back.

Incentivized

I used it

Incentivized

• Unification of toolset (one tool for managing software development defects and customer escalations)
• User appreciation for ease of use in finding interrelated issues amongst different product areas
• Users continue to express how ugly Bugzilla is, and while skins are readily available, none give a really polished feel to the system.

Incentivized