Join 34,000+ subscribers and receive articles from our blog about software quality, testing, QA and security.

Issues with Bugzilla and TestRails integration



We have recently purchased TestRails server edition. The current version in the lab is:
The Bugzilla version being: 5.0.3

When tried to PUSH a defect, an exception is thrown stating the ‘version’ is missing.

Here is the TestRail system log:
[BugzillaException] Invalid response (missing “version” parameter)

File: /var/www/html/testrail/app/plugins/defects/Bugzilla.php
Line: 422
Status Code: 500
Uri: /testrail/index.php?/defects/ajax_prepare_push (POST)

Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
PHP: 5.5.9-1ubuntu4.21
Server: Linux 3.16.0-77-generic #99~14.04.1-Ubuntu SMP Tue Jun 28 19:17:10 UTC 2016 x86_64

status_id: 1
version: 1.0.9
custom_step_results: [{“content”:“Check the downloaded patches list in the path given for downloading patches while the setup is in long-run.\n\n Ex: /home/qaops1/heat-local/patches”,“status_id”:“3”,“expected”:“All supported environment in the patch repository database should be downloaded depending on patch updates available.”}]
project_id: 2
test_ids: 4784
_token: XaXqa1tzAc3ycvMmcUe5

at Bugzilla_api->_throw_error (Bugzilla.php:387)
at Bugzilla_api->_check_version (Bugzilla.php:377)
at Bugzilla_api->__construct (Bugzilla.php:103)
at Bugzilla_defect_plugin->_get_api (Bugzilla.php:222)
at Bugzilla_defect_plugin->prepare_field (defects.php:682)
at Defects_controller->_prepare_form (defects.php:731)
at Defects_controller->ajax_prepare_push (controller.php:257)
at Controller->_invoke_web_call (controller.php:168)
at Controller->_invoke_web (controller.php:120)
at Controller->_invoke (gizmo.php:107)
at require_once (index.php:106)

Can you please help me resolving this. I am not sure what’s missing to get this fixed?


Hello Vivek,

Thanks for your post and for reporting the error! In order to get some additional details on the error, can you please enable system debug logs, and then reproduce the error:

You can then send us the log file directly to and we’d be happy to troubleshoot the issue and determine the cause. Please note that you should disable system debug logs after sending in the log file as they can be quite resource intensive due to the many lines that are written to the log file. Hope this helps!