Justin Sweeney 4LeafCoder April 14, 2005 Bugzilla http://www.bugzilla.org/ Mozilla 2.18 10 months personal experience 4 Free No special restrictions I know of Has a lot of potential for functionality, and easily supports new users or user groups I use a feature that exports the bug list into a comma-separated file (CSV) that can be viewed in Excel. Other features may be present I am not aware of. Web interface for users Fast, much faster in my experience than Test Director Can filter results by any field using Advanced Search Customizable searches with option to save them and re-query them anytime None that I know of We have never used this feature although it would have been advantageous to do so. The functionality may be there but I do not know of it. I attach pictures (.jpg, .gif, .bmp) and text files regularly, but have never been able to attach even a small video because of its size. None. Can decide which columns to display in bug list (ID, priority, reporter, assignee, etc.) and can sort by any column(s). UI has remained the same since my start at the company. None that I know of. None that I know of. Plenty. I personally turned off some of the notifications for sanity. Generic charting is available, never used. Generic charting is available, never used. Generic charting is available, never used. Yes, don?t know how difficult. Every complaint is handled by our in-house tech guru. Unsure. Bugzilla is a very good database. It doesn?t have a lot of extras or integration that I know of, but it runs very fast and effective queries. The generated bug lists (or tables as they prefer to call it) are easy to look through and are customizable so one can see the fields he or she needs to see. Users can create links easily in reports that will navigate people to other bugs or attachments that are relevant to a particular report. Our only problems are assigning read/write and other privileges. We wanted the ability to give individuals and/or groups rights depending on the situation. We may want a group to be able to read all bugs in one table but have to write to another, or maybe we want to allow a test lead to have the same privileges as the project manager on one product without having the test lead login to the project manager?s account. The only other disadvantage is that once a report is written, few fields can later be edited. Typically, a large number of comments are tacked onto the end of bug reports, and they too are non-editable. iBeta is an external QA house, so if I mention that there is not a feature that I know about, it may actually be available but we do not use it because our department is not responsible for any development. Also, I am not as familiar with Bugzilla as some others, so don?t take my comments as absolute gospel.