Who Should License The Personal Edition
If you are an individual developer using Bugzilla to manage one or more projects, the Personal Edition is for you. With it, you merely configure the connection to your database, set some properties and enjoy the benefits. The Personal Edition allows you to create an unlimited number of portlets, but only one dashboard. If you would like more than one dashboard, you should consider an Enterprise Edition license.
Licensing the Bugs Dashboard Personal Edition benefits a user in many ways, some of which are:
- Facilitates the interaction between you and your customers
- Assists in the communication of expectations to your customers
- Provides visibility into long standing issues
- Focuses resources on customer’s concerns
What to Expect
With each License, you will receive an e-mail within 1 business day with the URL to download your binary copy. You may wish to use the two-week evaluation copy to continue working during this time. The delay is necessary due to the workings of the payment transaction gateway. The Personal Edition requires a Java Servlet container (such as Tomcat). Once downloaded, you will unzip the .war file, move it to your deployment directory (e.g. webapps), restart your web server (if necessary) to expand the directory, then walk through the installation wizard (alternatively, you may hand edit the configuration files). You should backup your issue tracking database before you begin use of the Bugs Database and always test the installation first by moving only one issue then verifying the correct entries in your issue tracking system. You can move the issue back to its previous state after verifying the entries.You will receive 30-days of online (i.e. online chat or e-mail) and phone support. You may purchase additional ongoing support separately. Support contracts ensure that you receive all updates in that major version line. Upgrades are priced separately. Installation and User Guides are included within the zip file.
What You Need
At a minimum, you need a Java Servlet container, such as Tomcat. (Note: as of this time, Tomcat is the only container tested and certified.) A virtual private network (VPN) is not required unless you wish to access the Bugs Dashboard securely from outside the company’s firewall (e.g. your customer’s place of business). It is entirely possible to run the Bugs Dashboard on the internet (e.g. http://www.yourcompany.com/). We highly recommend that if you do so, you use a separate HTTP listener such as Apache in front of Tomcat and secure it with self-signed certificates at a minimum (i.e. use the Secure Socket Layer (SSL) to encrypt all traffic). The reason we suggest Apache is that you can configure it to not respond to the HTTP_TRACE command. We highly encourage you to consider, but do not require, a separate server for your database. The use of a separate server allows you to partition it off from the inter/intranet and gives you a little more protection from hackers.
You know your own issues better than anyone else, but managing those issues in the face of customer concerns can sometimes be a little bit like herding cats. We have years of experience putting our customer’s projects back on track and reinvigorating their relationships. Should you find yourself in a position where we can be of benefit, please have a look at our consulting agreement. You should always keep in mind that you’re embarking on process improvement, not simply installing a software package!
Additionally, we highly recommend that organizations purchase annual support contracts – and not because they benefit us, but because they benefit you! Annual support contracts ensure that you’re kept up-to-date with every update that we produce for that version. For example, if you license v2.0 and we put out 2.1, 2.2 and 2.3, you receive all three updates at no additional cost. We also focus on the business requests of our annual support holders first as we know they’re committed to the process of improving their organization.