Bugzilla

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.

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.

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.

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.

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.

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!

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.

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.

When you have absolutely no money to spend, Bugzilla is the best.

It's free and the most popular defect tracking system in the world which is under active development and support.

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.

I would suggest to ask how big the project is and how many versions and components are involved in doing so.

It is well suited for a small application. It needs to adapt like JIRA for large scale purposes.

It is very suitable for beginners and a firm smaller than 1000 employees.

Following points to be considerd before finalizing any tool:
1. Requirements
2. Users
3. Cost
4. Usability
5. Return of Investment

Great for quick issue tracking with review and QA. Not really suited for more modern agile projects.

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.