Bugzilla had many of the same common features necessary for bug tracking. However, the ease of use that JIRA provides while abroad is essential for many companies, and is the ultimate decision maker for those establishments. Additionally, while bugzilla includes a time setting …
We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but …
I didn't use other product like Bugzilla. so I don't have any other feedback on other products. But I would say Bugzilla is the best software that is for our company. We are using that, and we will use that too. So all the positive feedback. Thank you so much.
Bugzilla is very easy to use, very intuitive, and user friendly! For agile projects, the Kanban is very useful and you can drag and drop the defect to change his state. I work 10 times faster with Bugzilla.
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 …
JIRA from Atlassian, Quality Center from HP, TRAC were a few other tools that we had considered. The core features are present in almost all the competing tools. Bugzilla may not have a user interface as good as other tools, but serves the purpose very well as a bug tracking …
For most bug tracking systems, it stacks up pretty well considering the cost (it's free). But for a little investment, you can license JIRA which is far superior.
Bugzilla was free, so we selected it for the price and ease of implementation. We used many open source products, and Bugzilla was a good fit for the skill levels of our developers and easy for the team to use.
Buzilla is easy to use and provides basic functionality to use as a bug tracking tool. If big size attachments are allowed it would have been great. Also with Bugzilla home->Test management area is improved by allowing multiple sections it would be awesome!
Open source! No license fee involved, no limit to the number of licenses.
Easy to install and maintain. Installation is very easy and hardly needs any maintenance efforts, except when migrating from one version to other. Each project can have its own group of users.
Includes all the core features/fields that are needed to log a software bug/issue.
Multiple attachments are possible, supports various formats.
Good for reporting. Filtering mechanism lets you query bugs by various parameters.
Cloud Based. I'd like to see bugzilla be cloud based. The company I currently work with made a final decision to change db's for this specific reason. Due to the frequency of travel in this company, they need access to bugzilla from differing national / international locations.
Larger File Attachments. I believe the limit of a bugzilla content upload is 4 megabytes. For many of our video'd issues, this file size is simply impractical without the additional effort exertion on video compressor applications.
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.
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.
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
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.
We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but because the organization was looking for cost savings, we ended up going with Bugzilla and it's FOSS model so as to avoid ongoing costs.
It has made the SDLC process more efficient. Bugs were logged and tracked in emails or in Excel sheets leading to slow communication and at time version issues with multiple files. Being an online tool, Bugzilla solved those issues, improved communication, instant status updates and improved efficiency.
We have used Bugzilla with a lot of federal goverment agencies (DHS, CMS, SAMHSA, CDC, HHS etc). Project Directors adn Principle Investigators were at times given access to Bugzilla which provided a snapshot of open vs closed issues.
Some groups would resist using Bugzilla with the email reminders being the main reason. Turning off or reminding them of features where we can 'control' email notification helped a lot.