Bugzilla, or nah?
Pros
- 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".
Cons
- 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.
Return on Investment
- Truly serves its purpose for local bug tracking.
- Ability to trace conversations with time stamps relinquishes the common burden of tracking release fixes.




