Steven Yong's Weblog

Just experienced that setting up Bugzilla isn't as straight forward as it should be. The code you can get from Bugzilla.org is just a part of the entire system. Finally I managed to get it running on my Windows XP machine.
Basically these are what we need to have in order to get it works:

• Bugzilla codebase (core module, written in Perl)
• Apache httpd 2.x (handling http requests since Bugzilla is a web based system)
• ActivePerl (executing Perl script)
• MySQL 4 or higher (bugs database)
• Some perl modules like MailTools, Chart and etc.

The home page after logged in, yeah I know it isn't attractive and user-friendly enough



Have a new project? (unfortunately Bugzilla uses the term "Product" for both project and product), here is the page to go.



A friend of mine just posted me a very interesting question saying that how can we handle change request or any other non-bug issue in Bugzilla. Too embarrassed to say that I couldn't figure out a good way of handling that and the only acceptable method I found is resolving the bug with a status you want, for example "remind" or "later". But the issue will be inaccurately marked as "resolved" which can be a very risky bug status for your project.


I guess more document reading have to done in order to master this open source tool. Frankly speaking I never think that I'd ever use CGI based system for work anymore, thing always hard to predict.