Connecting TestLink 1.9.5 to JIRA bug tracker

Other Questions Jira
1

I’m having trouble setting up TestLink 1.9.5 to work with JIRA. I’ve tried to configure it in the issue tracker management section but no luck. Here’s what I put in the config:

<bugtracker>
  <login>myuser</login>
  <secret>mypass</secret>
  <baseurl>http://jira.mycompany.com</baseurl>
  <soapurl>http://jira.mycompany.com/soap/services/jirasoapservice-v2?wsdl</soapurl>
  <viewurl>http://jira.mycompany.com/browse/</viewurl>
  <createurl>http://jira.mycompany.com/secure/CreateIssue.jspa</createurl>
  <projectid>PROJ123</projectid>
</bugtracker>

When I test the connection it says ‘Connection is KO, check configuration’. And when I try to use it during test execution I get an error about not being able to connect to the bug tracker.

Any ideas what I’m doing wrong or how to fix this? I really need to get TestLink and JIRA talking to each other. Thanks!

2

hey mate, had similar issues. check ur firewall settings - might be blocking the connection. also, try using http instead of https in the urls. sometimes that fixes it. good luck!

3

I encountered a similar issue when setting up TestLink with JIRA. Have you verified your JIRA credentials are correct and have the necessary permissions? Sometimes it’s not just about the configuration, but also about user access rights. Additionally, ensure your JIRA instance is compatible with the TestLink version you’re using. Incompatibility can cause connection failures even with correct settings. If possible, try setting up a test JIRA project solely for integration testing. This can help isolate whether the issue is with your production JIRA setup or the TestLink configuration itself. Lastly, check your TestLink logs for any specific error messages that might provide more insight into the connection failure.

4

I’ve dealt with similar integration issues before, and it can be frustrating. One thing that jumps out to me is the SOAP URL you’re using. In my experience, TestLink 1.9.5 often has trouble with the SOAP v2 endpoint.

Try changing your soapurl to use the v1 endpoint instead:

http://jira.mycompany.com/rpc/soap/jirasoapservice-v2

Also, double-check that your JIRA instance has the SOAP API enabled. Some admins disable it for security reasons. If it’s off, you’ll need to work with your JIRA admin to get it turned on.

Lastly, make sure your TestLink server can actually reach the JIRA URL. Sometimes firewall rules or network segmentation can cause connection issues that look like config problems.

If none of that works, you might consider upgrading TestLink. The newer versions have better JIRA integration that doesn’t rely on the older SOAP API.