1) Remember that the script "script/bugzilla_api_server.pl" must be invoked before starting the connector. Starting the connector without running this script will generate an error (like "can not connect to server").
To run the script, issue two commands, something like: cd /var/www/0.9 script/bugzilla_api_server.pl
2) Navigate to this URL in your browser: http://localhost:3000/ . Does the "Welcome to the world of Catalyst." display?
The banner should look something like: Bugzilla::API on Catalyst 5.80030
3) Navigate to this URL in your browser: http://localhost/bugzilla/ .
The "Welcome to Bugzilla" page should display:
4) Navigate to this URL in your browser: http://localhost:3000/bug/37000/ (again, please use your value for localhost:port).
You should see the details page for bug id "37000", which looks similar to:
5) If the Bugzilla API is installed properly, one of these two URLs will be accessible:
6) The "json_pure" Ruby Gem must be installed on your system. And it should be version 1.2.4 (that is the version which passed all of our Bugzilla tests).
To view the Ruby Gems installed on your system, use this command:
7) If your site uses a proxy server to connect to Bugzilla:
- The connector itself does not have the capability to use proxy authentication.
- Your IT department may be able to enable access to your Bugzilla server if a proxy is involved.
8) What version of Bugzilla API have you installed?
Please note that we have tested 0.9 and 1.0 only.
9) There is a custom field which must be created in Bugzilla, which will contain the Rally ID of any bug copied from Rally to Bugzilla.
The "Type:" of this field must be "Free Text", and NOT the somewhat mis-leading "Bug ID" type,
which is the default type used if "Free Text" is not specifically selected.