JIRA Integration - Common Roadblocks and Potential Solutions

This is a guide to common issues faced when setting up an integration for qTest to JIRA.  If you are looking for a detailed guide of setting up this integration, please navigate here: Integration with Jira.

Many of our qTest customers currently rely on our out of the box integration with JIRA for pulling requirements into qTest and logging defects back into JIRA.  Our integration with JIRA is consistently applauded as the most stable and robust of the test case management solutions on the market, but even so, with the number of moving parts and variables in customers' JIRA instances, there are a number of reasons why your JIRA integration may fail when you initially set it up.  Below are some of the most common issues our customers experience with their JIRA integrations:

 

Index:0, Size: 0 error shown in qTest JIRA connection dialog: Make sure that the JIRA account being used for integrating with qTest has JIRA System Administrator Global Permissions assigned to it.  This error usually presents itself when the account being used for the integration doesn't have permissions to create objects in JIRA that will be mapped to defects (issues, tasks, etc.)

Connection failed. Received fatal alert: bad_record_mac shown in qTest JIRA connection dialog: This issue usually presents itself when JIRA is using SSL encryption.  We are currently building in encryption into our integration, but for now, we will currently have problems with JIRA instances using SSL.  Please contact our support team (support@qasymphony.com) and we will explore options with you for getting this integration set up while maintaining the security and integrity of the data in your JIRA instance.

On-Premise JIRA system crashes when setting up qTest for JIRA add-on: This usually occurs when the JIRA On-Premise version is hosted by a 3rd party provider or hosting service, which will enact stricter time out limits on record retrievals.  Not to worry, we have packaged a separate connector that will resolve issues with this integration.  Again, please contact us at support@qasymphony.com and we will be happy to help you with resolving this issue.

On-Premise JIRA to On-Premise qTest connection successful, but cannot retrieve requirements into qTest: This issue is specific, and only appears infrequently, but we have been able to resolve it by reinstalling qTest on-Premise.

Issue Connecting from On-Premise JIRA to On-Demand qTest: Usually, this issue is caused by incorrect firewall settings.  Please open the firewall to these IP's to allow qTest to communicate with your On-Premise JIRA instance: 

  • 54.83.56.253
  • 54.83.57.47
  • 54.83.57.78
  • 54.83.57.122
  • 54.83.57.143
  • 54.83.57.153

qTest to JIRA Integration fails due to "Invalid Credentials": This often happens when a customer is using a JIRA account that is validated by single sign on (Crowd) .  We usually instruct the customer to create a new Admin account directly in JIRA, and use that for the qTest integration, when possible.

 

Please feel free to contact us if you experience any issues with your JIRA integration that were not mentioned above, we are happy to help you out.  You can reach us through qTest by the "Submit Ticket to QASymphony" button, or via email at support@qasymphony.com.