Overall Satisfaction with Bugzilla
It is being used by the eCommerce team to manage tasks and bugs. It helps with the workflows between project managers, business owners, software developers and quality assurance. It is used globally across the different regional teams that the global team supports.
- Software Workflow. Bugzilla has some lightweight workflow that allows you to follow a specific. In lieu of using nothing, it provides some structure.
- Project Management. Bugzilla allows PMs to organize what needs to be done and when.
- Metrics of software team effectiveness. The reporting, while not robust, does allow for burn down charts on other measures of effectiveness. For example, if you want to know the number of reopens, Bugzilla can do that. While not the most telling, it can help give you an idea.
- 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.
- Makes the team more effecient
- Increases visibility to the organization of what's going on.