Bugzilla

We work for an automation testing project here in TechMahindra. We log our defects in Bugzilla and it's very easy to understand for the development team when they review them.

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.

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.

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.

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.

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!

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 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.

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.

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.

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.

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.

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.

BugZilla is used in the Software Engineering team to address key defects and loopholes.

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 as overall solution for defect tracking and delivery. It helped the organization in managing entire testing drive in a very cost effective way.

Bugzilla is being used as one of the bug tracking or issue tracking resources that development teams may use for projects.

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.