A software project management system used to plan, track and release great software with this lightweight and customizable system that integrates into any project management workflow. FogBugz is designed for software development teams and includes all the project management tools developers need straight out of the box. Users can: Track projects from start to finish - With tasks and subtasks for each case with required details and track them to ensure…
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.
Fogbugz is great for case-and-task based businesses. If your business has hundreds of weekly anticipated tasks that exist, such as processes to get files converted, Fogbugz can manage these processes very well. For our team, we knew each week that we would have about 500 tasks or orders to get processed. Fogbugz helped us break down these projects, get them assigned evenly throughout the team, and easily see who is working on what task. FogBugz is also good for tracking unanticipated tasks like bugs, making notes, flowcharts, and categorizing if the problem is a bug, feature request, etc. For us, it was just the best at nailing down those anticipated tasks.
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".
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.
Workflow capability is very limited to the original implementation, could use a refresh and extension of the capabilities
UI/UX needs improvement. This was in the works prior to purchase by DevFactory, and has taken a back seat to backend improvements that rightfully needed to be fixed first.
Pricing model doesn't fit our usage very well, so we're paying for full-featured users for everyone even though the majority of Users only need to submit Cases and modify the Wikis, and our small percentage of Users are in Dev and need all features.
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.
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 back.
FogBugz is made for the Developers who actually use it every day, while JIRA is made for the C-Suite who oversees them but has little idea of the finer points of daily dev tasks. In reality, most don't fit into the mold of JIRA tickets, and the summarized information that C-Suite is reviewing is incomplete or skewed. There is also an outstanding issue since 2004 that JIRA refuses to implement despite wide user support, the merging of tickets. You can see the open ticket with the JIRA team here: https://jira.atlassian.com/browse/JRACLOUD-3592
