Bugzilla

Bugzilla

Score 7.1 out of 10
Bugzilla

Overview

Recent Reviews

Bugzilla

9 out of 10
March 29, 2017
We are using it for the bug tracking in our project. It is used in our engineering department, for software bug report and tracking.
Enginee…
Continue reading
Read all reviews

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Bugzilla, and make your voice heard!

Return to navigation

Pricing

View all pricing
N/A
Unavailable

Sorry, this product's description is unavailable

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

1 person want pricing too

Alternatives Pricing

What is GitLab?

GitLab is a complete open-source DevOps platform, delivered as a single application, fundamentally changing the way Development, Security, and Ops teams collaborate and build software. From idea to production, GitLab helps teams improve cycle time from weeks to minutes, reduce development process…

Sorry, this product's description is unavailable

Return to navigation

Product Demos

Bugzilla Tutorial - 1 - INTRODUCTION | WHAT IS BUGZILLA
01:42
Return to navigation

Product Details

What is Bugzilla?

Bugzilla Video

What is Bugzilla?

Bugzilla Integrations

Bugzilla Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

BugTracker.net, Gemini, and Jira Software are common alternatives for Bugzilla.

Reviewers rate Availability and Usability highest, with a score of 9.

The most common users of Bugzilla are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews

(1-18 of 18)
Companies can't remove reviews or game the system. Here's why
April 19, 2017

Bugzilla, or nah?

Isaiah Hayes | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Bugzilla was used as a bug management system for our clients (ranging between 50-250 clients). This was used to track the progress of all of our projects; when issues were ticketed, worked on by the appropriate team member, resolved, retested and closed. It was also used as a primary system for company communication as it related to our project issues.

We were able to use it while team members were out of state, as well as out of the country.

It helped us solve organization problems with our bugs, and kept us aware of any outstanding issues by taking advantage of the "status" section of Bugzilla.
  • 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".
  • 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.
If a company has a need to test a product with many variations (web, mobile, kiosk, etc.) bugzilla makes the "product" alternation easy to access. However, accessing said projects without access to the company's internal server is incommodious.
Score 7 out of 10
Vetted Review
Verified User
We use Bugzilla departmentally both as a defect tracking tool and as a customer escalation tracking tool. Because the two categories of issues are often interrelated, we found that one type of issue often becomes another, and vice versa. This helped streamline our process between our customer support organization and our software development organization.
  • Customization of fields
  • Flexibility of permissions system
  • Ease of use
  • Bugzilla UI continues to look dated out of the box. Engineers want pleasant to use tools, not something that looks designed for the early days of the web.
  • Bugzilla administration continues to be a pain point. We have needed to dedicate one engineer with a specialized skillset to manage Bugzilla.
  • Bugzilla could get some features to make it easier to bulk add items to the database - we use other third party tools that interface with Bugzilla to do this, but at a cost to the organization.
Bugzilla is well set up to support multiple related projects within an organization, perhaps even just as different components of a larger software package. With the flexible permissions model, Bugzilla is well set up to provide separation of concerns between projects, while providing ease of information sharing between interrelated areas. Users of a system configured as such will find that their workflow is streamlined by not having to leave a given system to enter their defect against a different area.
March 29, 2017

Bugzilla

Score 9 out of 10
Vetted Review
Verified User
We are using it for the bug tracking in our project. It is used in our engineering department, for software bug report and tracking.
Engineers can report bugs and create bugs. After they fix the bugs, they can change the status of the bugs. Also you can create a list bugs that were created before.
  • bugzilla can track our bugs that are generated during the development.
  • It is easy to use and maintain.
  • More customizable.
  • Editing sometimes is hard.
  • Big attachments cannot be uploaded sometimes.
We had a bug that a customer reported. It happens on our customer side about once every 100 times, so it is very hard to repeat issue on our side. Then we go back to check our Bugzilla, and check every change we did in the past, and it is easy for us to find the issue.
Sarah Ciras Rousseau | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
I used Bugzilla as a contractor of CK-12. It was fairly easy to get started with remotely. It is an organized system that helped in keeping all of the known items separate and clearly labeled for the Quality Assurance team and my supervisors to review the work efficiently. It helped keep everything straight.
  • It is organized.
  • It is a clean interface.
  • It is easy to get started with.
  • Could be more customizable.
  • Have easier coordination between users.
  • More user accessibility features.
Bugzilla worked well for what we used it for. It gave a better way to organize the tasks we created and allowed for an easier workflow. It, however, had many fields we did not personally utilize, so being able to pare it down would have helped to streamline the work further. Being able to personalize this would help.
Score 8 out of 10
Vetted Review
Verified User
I’ve used Bugzilla at two big projects in my company, and both times have loved how it’s handled our sprint planning, tracking, and review. It has good integrations, custom workflows, and can function well for internal and external use. I also like the Agile plug-ins which provide the ability to use SCRUM or Kanban to manage software projects. Bugzilla allows you to be quite organized, which can be crucial when working with hundreds of tickets. The tools are so in depth and complete, it's pretty amazing!
  • It is a great place for our development team to keep track of the cases they are dealing with.
  • Very easy to install and configure.
  • The ability to integrate with other softwares.
  • Editing flows is hard.
  • It can be challenging to navigate and slow occasionally.
  • Personally I don't like the reports and its formatting.
Pretty much issue tracking, better visibility into outstanding workload. It allows us to stay organized and to assign tickets to specific people or teams. Bugzilla also helps to monitor workload and review time spent on tasks.
Score 9 out of 10
Vetted Review
Verified User
Bugzilla is being used in my department, other departments use JIRA for bug tracking. The problem we have is test management integration with our own testcase repository (previously used HP Quality Center which worked well with Bugzilla, but currently using Testopia which was developed by our company engineers which does not integrate test cases with Bugs reported).
  • Bugzilla is easy to use and access
  • Bug search criteria is very efficent
  • Renaming and saving each bug search thread is useful
  • The UI of how bugs are listed, especially allowing the option to change columns, edit search is very useful
  • Big attachments cannot be uploaded.
  • When two people update the bug at same time it throws both the changes - instead if it can save one and ask the other to save again would help.
  • When we scroll to view the bug, it would be nice if the heading of the bug is showing/static while we scroll down to view the contents of bug comments.
  • Bugzilla home link needs improvement in Test Plan,test run creation - currently we can upload the test plan and link to each test run iteration - if it allows multiple selection of test runs to one test plan it helps.
  • Drag and drop of test cases to test run is very inconvenient as we have to manually drag each test case to test run. If multiple test cases can be checked and moved to Test run it would be helpful.
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!
Sharmin Promi | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
Bugzilla is used for the product and development team of the organization. The tool is mainly used for defect tracking, maintaining and documentation of issues from the users point of view.
  • Open source tool. No license required. Easy to install and use for new users.
  • Great tool for defect tracking and managing defects. Well organized and very user friendly.
  • Well manageable and reports of defect are exportable.
  • Great for managing multi-project level defect tracking.
  • Improvement required for reporting and filtering area.
  • Improvement required in customizing dashboard according to users preference.
  • Improvement required for project level documentations.
Bugzilla is well suited for small project, small companies and where other tools is used for BRD and FRD documents.

Less suited or not suited where everything is needed to be done on same platform.
Anwar Mohammed, PMP | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We have multiple groups/departments within the company. Most groups that do some software development or maintenance use Bugzilla as a bug tracking tool. Being open source, and our company being a non profit, it serves our purpose very well. Some groups have started using JIRA (which was also offered without any cost towards the license).
We have used Bugzilla on multi million contract projects, without any issues. Our federal government clients also have access to some of the projects (issues) to track the status of open/closed bugs.
  • 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.
  • Dashboard - If a landing page with a graphical display was available for use by management, that would help a lot.
  • Customizing - Need more flexibility with customizing fields (renaming, adding etc).
  • Workflow - If we could have templates that could be followed by various projects (which is how organizations work), that would encourage more project teams to adopt usage of Bugzilla.
  • Add/Filter Enhancements or Requirements - Often times an enhancement is logged that is not a bug, but this cannot be distinguished easily. Provide option to log not just a bug, but also Enhancements or Requirements.
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.
Josh Zapin | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
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.
When you have absolutely no money to spend, Bugzilla is the best.
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.
Score 9 out of 10
Vetted Review
Verified User
Our department uses Bugzilla to trace all development and bug fixing progress. And by connecting with the source control system to trace all checkins. With the add-on extension Testopia, test cases and test plan/progress also gets properly traced.
  • Easy to trace development and bug fix efforts
  • Simplify communication between developer, tester and customer support
  • With add-on like Testopia more development activities get traced
  • Better format of comments
  • Possibility to update existing comments?
It's free and the most popular defect tracking system in the world which is under active development and support.
August 16, 2014

Bugzilla at its best

Score 8 out of 10
Vetted Review
Verified User
Bugzilla is used to address all the internal technical issues and bugs raised in each project that our organization holds. It is a very good and flexible tool. It can be used in many different ways and can be configured as per the department process. Since it is open source, I have customized it according to our SQA process and is liked by all the top level management.
  • Tracking status of each bug
  • Configurable and customizable
  • Interface
  • Flexible Search
  • More attributes that can be configured
  • Better Default Layout, to avoid customized layout
  • Search by more parameters
Specific Scenarios - It was flexible enough to configure and customize as per our department/organization SQA process, which makes it a key thing for selection.
August 15, 2014

My Bugzilla Review

Ian Ximinies | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
We used Bugzilla across the whole organization for the most part. I found it to be very good at what it did. We used it to track open issues as well as adding new features to products and services that we were launching. I think it is very helpful with the way it captures and sorts information, project and version number, and is a very easy tool for QA and Dev to use to communicate back and forth with each, either with direct notifications or group emails. The one knock I had for Bugzilla is that sometimes building custom search queries that entailed a lot of greater or less than status became very hard when dealing with extended version numbers of certain products that were saved in Bugzilla.
  • Status of an Issue
  • Tracking an Issue
  • Easy simple searches
  • Complex Query Searches sometimes dont yield the results that you expect
I would suggest to ask how big the project is and how many versions and components are involved in doing so.
Anand Safi | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
BugZilla is used in the Software Engineering team to address key defects and loopholes.
  • Defect Management
  • Great status tracking
  • Easy and Clean UI
  • Needs a clean and better UI
  • Needs a proper severity/prioritization criteria
  • Needs better integration with Test Case Management tools
It is well suited for a small application. It needs to adapt like JIRA for large scale purposes.
Shailesh Patel | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Bugzilla was used by the QA department when we tested the Remedy application and logged the defects/issues found during the testing.
  • Bugzilla was used to log the issue from customers, internal code error and other environmental issues.
  • It helps to track the issue, progress the issue and monitor the issue for long run.
  • It is very strength full tool I think.
  • It is very friendly user and nice to have it.
  • I think you should compare the defect module structure with Quality Center Defect module and structure and modify according to it.
It is very suitable for beginners and a firm smaller than 1000 employees.
  • In-person training
I prefere this.
No
Amit Sardesai | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Bugzilla was used as overall solution for defect tracking and delivery. It helped the organization in managing entire testing drive in a very cost effective way.
  • Open Source
  • Easy configuration & User friendly
  • Flexibility & Customized defect flow possible as per project need
  • Email server conectivity through different servers possible for defect update mailer
  • Test Management Integration specially test case management
  • Performance issues
  • Support can be improved
Following points to be considerd before finalizing any tool:
1. Requirements
2. Users
3. Cost
4. Usability
5. Return of Investment
Tom Printy | TrustRadius Reviewer
Score 5 out of 10
Vetted Review
Verified User
Bugzilla is being used as one of the bug tracking or issue tracking resources that development teams may use for projects.
  • Good at issue tracking.
  • Ease of use for logging issues.
  • Easy to use and maintain.
  • Feels old. The UI could be improved
  • Needs the ability for product owners to add custom fields to issue reports
  • Would be neat to have an agile burn down chart.
Great for quick issue tracking with review and QA. Not really suited for more modern agile projects.
Barrie Byron | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
We used Bugzilla for the product development team and the information development process. We entered bugs to track requested product changes, including user interface changes, functional defects, and enhancement requests. We also used Bugzilla to track and monitor our documentation changes for each release cycle, and to track documentation defects.
  • Bugzilla provides visibility to product change requests, including user interface changes.
  • Bugzilla provides metrics and audit trails for issues.
  • Bugzilla keeps all notes related to a specific issue in a single place. Changing ownership of an issue is easier with Bugzilla, and certainly is more simple than sending a chain of emails.
  • Bugzilla comments are plain text, so at least a rudimentary understanding of markup is required. Rich text and enhanced symbol support would offer more flexibility.
The price is right! Open source allows a new team to get up and running for bug tracking from day one. Custom skins make the product feel like your own.
Score 8 out of 10
Vetted Review
Verified User
  • It has a clean interface that customer service can input support tickets in regards to tech issues on the site.
  • Ability to go back and forth with the developer = less meetings & more productivity.
  • Nothing.
  • Self-taught
There is no technical support per se - which is OK for a pretty simple product like this. They do offer things like user forums and Q&As which are effective enough.
Return to navigation