Mantis Bugtracker 

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008760TestLinkBug Tracking System - JIRA Integrationpublic2019-09-10 14:192020-03-08 10:46
Assigned Tofman 
StatusresolvedResolutionno change required 
PlatformLinuxOSgentooOS Version
Product Version1.9.19 (2019 Q1) 
Fixed in Version 
Summary0008760: Unable to Create or Link JIRA Issues to Testcases
DescriptionI followed the tutorial [^]

Therefor I used the JIRA SOAP Connection.

The configuration for my Issue Tracker in TestLink looks like:

<!-- Template jirasoapInterface -->
<uribase>https://myurl/jira/</uribase> [^]
<uriwsdl>https://myurl/jira/rpc/soap/jirasoapservice-v2?wsdl</uriwsdl> [^]
<uriview>https://myurl/jira/browse/</uriview> [^]
<uricreate>https://myurl/jira/secure/CreateIssue!default.jspa</uricreate> [^]
<!-- Configure This if you want be able TO CREATE ISSUES -->

Steps To ReproduceAfter configuration the "Check Connection"-Button shows me OK.

When I execute a Testplan I see the buttons to create and add JIRA issues

When I click on button to create a jira issue the popup opens

When I click on the save button, I got an error text (see Screenshot 03)

Error text:

Create JIRA Ticket FAILURE => Error finding "uri" property - serialized issue:a:5:{s:7:"project";s:3:"TST";s:4:"type";i:0;s:7:"summary";s:78:"Meldunginformationen anzeigen - Executed ON (ISO FORMAT): 2019-09-10 15:18:27";s:11:"description";s:0:"";s:9:"issuetype";i:1;}
Additional InformationAfter the error I get a nginx/1.17.3 error "502 Bad Gateway".

In the error-log file I find this line:
2019/09/10 15:17:38 [error] 4000#4000: *1866 FastCGI sent in stderr: "PHP message: PHP Warning: Invalid argument supplied for foreach() in /var/www/localhost/htdocs/testlink/lib/functions/logger.class.php on line 202" while reading res>

TagsNo tags attached.
Database (MySQL,Postgres,etc)MySQL
BrowserFirefox / Vivaldi
PHP Version7.3
QA Team - Task Workflow StatusTBD
Attached Filespng file icon 03_Error_Creating_JIRA_Issue.png [^] (34,875 bytes) 2019-09-10 14:19

- Relationships

-  Notes
fman (administrator)
2019-09-10 15:33

My first advide is avoid SOAP (because I has been deprecated in JIRA) and move to the REST API.

I can not do test with SOAP because is not supported by jira on cloud
testerav (reporter)
2019-09-10 15:43

I don't connect to JIRA on cloud, I connect to your own instance.

I sadly couldn't find the blog post, but I read, that I should use SOAP instead of REST?
testerav (reporter)
2019-09-10 15:44

And by the way, we are still useing an older version of jira (v5.2.11).

Could that be a problem?
fman (administrator)
2019-09-10 16:10

I do not think that JIRA version can be an issue, but the kind of support I can provide is limited because the only platform I've to test JIRA integration is on Cloud with REST.
I'm sorry
fman (administrator)
2019-09-10 16:11
edited on: 2019-09-10 16:11

may be you can contact reporter of 0008759, because it seems he is using jira with SOAP

testerav (reporter)
2019-09-17 08:17

I tried to use REST, but I have the same issue as mentioned in 0008742, that I get the error "Test Connection KO".

Can you give me some hints for debugging, where I can find the real error message, why the connection could not be created?

fman (administrator)
2019-09-17 17:50

Only thing I can do is test against my jiracloud and provide the configuration I've used.
fman (administrator)
2019-09-17 19:38

<uribase></uribase> [^]
<uriapi></uriapi> [^]
<uriview></uriview> [^]

with this config I've no problems
testerav (reporter)
2019-09-18 07:08

with your configuration I also didn't have a problem.

Which Request did you send against jira when clicking on the "Check connection" button?

Is there a possibility to see in a logfile if there is an authentification issue or a connection issue?
fman (administrator)
2019-09-18 10:35

Be careful with JIRA Changes because user password is not used anymore for REST but you need to use the APIKEY in place of password.

For the log best thing to do is add debug info for yourself in the JIRA interface files, because standard log is not provided by testlink

testerav (reporter)
2019-09-18 13:31

Ok, this could be my issue, I used my userpw in <password> </password>

But I have to use a standalone jira server instance and didn't get an APIKEY. I'll try to get one from my IT support, because I couldn't find it on my jira account page.
fman (administrator)
2020-02-21 21:12 [^]
fman (administrator)
2020-03-08 10:46 [^]

- Issue History
Date Modified Username Field Change
2019-09-10 14:19 testerav New Issue
2019-09-10 14:19 testerav File Added: 03_Error_Creating_JIRA_Issue.png
2019-09-10 15:33 fman Note Added: 0029145
2019-09-10 15:43 testerav Note Added: 0029146
2019-09-10 15:44 testerav Note Added: 0029147
2019-09-10 16:10 fman Note Added: 0029148
2019-09-10 16:11 fman Note Added: 0029149
2019-09-10 16:11 fman Note Edited: 0029149 View Revisions
2019-09-17 08:17 testerav Note Added: 0029163
2019-09-17 17:50 fman Note Added: 0029169
2019-09-17 19:38 fman Note Added: 0029170
2019-09-17 19:38 fman Assigned To => fman
2019-09-17 19:38 fman Status new => feedback
2019-09-18 07:08 testerav Note Added: 0029171
2019-09-18 07:08 testerav Status feedback => assigned
2019-09-18 10:35 fman Note Added: 0029172
2019-09-18 13:31 testerav Note Added: 0029174
2020-02-21 21:12 fman Note Added: 0029504
2020-03-08 10:46 fman QA Team - Task Workflow Status => TBD
2020-03-08 10:46 fman Note Added: 0029525
2020-03-08 10:46 fman Status assigned => resolved
2020-03-08 10:46 fman Resolution open => no change required

Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker