Bugzilla vs. Digital.ai Agility

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

Digital.ai Agility is an ideal tool for anyone who is looking to track the work of a software development team following agile processes. It easily supports multiple teams with multiple backlogs, but also allows aggregation and rollup across those teams for larger analysis and planning.

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

• Automated saving of changes, no records can be lost because all items are saved in real-time.
• The watch function, optional but beneficial when managing multiple teams or projects.

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

• Saving of changes is inconsistent. Sometimes the changes appear to save automatically and other times the user needs to click the "Apply" button. Until the user is familiar with when this needs to happen, work can easily be lost.
• This may be a setup configuration issue, but it would be good to be able to set the default team when creating stories. Too often stories are created and the user forgets to enter the team and they need to search the entire database for the story that was just created.

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

VersionOne provides outstanding training. They have Product Owner training that I recommend every Product Owner attend. They have scrum master training and other agile training that was well worth the money paid because it made the teams more productive. And the support for the tool is incredible. These people live and breathe Agile and are evangelists and enthusiasts.

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

We considered rally & AgileCraft since they also provides good support to SAFe framework. Though I personally found Rally better equipped but Rally was rejected due to its higher cost. AgileCraft & Version One provides many common features i.e Team Rooms, Planning Rooms, Capabilities Kanban, Road mapping but Version One support for collaboration tools & its seamless integration with GitHub played key role in going with Version One.

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

• At first, it was difficult for the teams as we were learning Agile and VersionOne. But VersionOne provided us with great training and support. As such the teams were able to quickly adopt and embrace Agile.
• Our teams are now more efficient.
• Our time to market has decreased significantly.

Incentivized