[SOLVED] Testlink 1.9.5 and JIRA : Not able to create issues

[JQA]

Hello.


Well, I recenttly updated to Testlink 1.9.5 . I finally configured the issue tracker, jira , in SOAP (didn't find REST type). And I found that I am not able to create issues again... (but able to link them as usual). As I read in the release notes, It seemed it to be possible... My questions are :

- Is it really posible to create issues from Testlink via API for JIRA?
- Is it possible to connect them viar REST?


Thanks in advance.

[fman]

1. API , only SOAP (never talked about REST)
2. missing description of MANDATORY config parameter <projectkey></projectkey> con XML configuration
ANYWAY without this key YOU HAVE TO See the new icon (see image)
https://docs.google.com/open?id=0B-hNfK ... EhmNUlwaHc
and you have to get AN ERROR if you try to use new icon

[mtavares]

I have a similar issue:


I can linked a Jira Bug to testlink and it works perfectly through SOAP. However, I can not use TestLink to create a bug in Jira.

What format do I need to use in the config to specify the project PID and Issue Type?

I imagine I would need to specify additional information in the <uricreate>?

I tried adding the following to <uricreate>:

jira/secure/CreateIssue.jspa?pid=10781&issuetype=6&Create=Create and I get SOAP Fault: (code: WSDL, string: SOAP-ERROR: Parsing WSDL: Couldn't load from '/rpc/soap/jirasoapservice-v2?wsdl' : failed to load external entity "/rpc/soap/jirasoapservice-v2?wsdl" )


I get this error when trying to add a Jira Bug via TestLink using when I don't specify the project in the config:


Create JIRA Ticket FAILURE => com.atlassian.jira.rpc.exception.RemotePermissionException: The project specified does not exist or you don't have permission to create issues in it. - serialized issue4:{s:7:"project";s:0:"";s:4:"type";i:1;s:7:"summary";s:193:"/ECM/Browse/Add To List/Collection/ECM-1921:Browse Collections - Verify that user is able to navigate to collection page when clicking 'Browse C - Executed ON (ISO FORMAT): 2012-12-18 16:39:59";s:11:"description";s:166:"Execution ID: 560 Tester: mtavares Test Plan: mike3 Platform: Chrome 18 Build: 1 Executed ON (ISO FORMAT): 2012-12-18 16:39:59 Execution Status: failed ";}

[fman]

in previous post what explained may be not as clear as needed that :
>> missing description of MANDATORY config parameter <projectkey></projectkey> con XML configuration
we said nothing about pid and adding to any uri.
complete example:

<issuetracker>
<username>testlink.forum</username>
<password>forum</password>
<uribase>http://testlink.atlassian.net/</uribase> [^]
<uriwsdl>http://testlink.atlassian.net/rpc/soap/ ... l</uriwsdl> [^]
<uriview>http://testlink.atlassian.net/browse/</uriview> [^]
<uricreate>http://testlink.atlassian.net/secure/Cr ... /uricreate> [^]
<projectkey>ZOFF</projectkey>
</issuetracker>

see mantis issue 5434

[mtavares]

fman,

This works for me, thanks for the help. I can successfully link and create new issues in Jira. Is there any plans to add the test case steps to the bug in the near future? Currently, when I create a Jira bug via TestLink, I don't see the Steps. it would be helpful if the Steps got added to the Bug description in Jira.

[fman]

there are no plans to add more info to issue created automatically.
IMHO adding test case details on issue is not a GOOD good idea,due to duplication of information that will be easy out of sync.
IMHO reference to test case is enough.

If you have some custom development that you need and that you are able to sponsor, contat us.

[mtavares]

Thanks,

I think you make a fair point. I am not opposed to having my team contribute some code or a sponsorship if there is something we have to have. REST API for JIRA might be big one, as SOAP is being deprecated and no longer actively supported in JIRA 5.

FYI, in case this helps someone, we also had to put this field: <issuetype>6</issuetype> in the Jira Issue Tracker Management config to get it to work. We kept getting wrong issue type errors prior to making this change.

[fman]

issuetype theorically has to be initalized with default type in the TL jira class.
That's why I've not made clear that also this config parameter is available.
I'm going to check.
It will be OK to develop the REST API for JIRA through sponsorship.

[abrjib0]

Hi,
I have configured JIRA as below.
<!-- Template jirasoapInterface -->
<issuetracker>
<username>user@client.com</username>
<password>Abc@123a</password>
<uribase>https://jira.grc.client.com/</uribase>
<uriwsdl>https://jira.grc.client.com/rpc/soap/ji ... l</uriwsdl>
<uriview>https://jira.grc.client.com/browse/</uriview>
<uricreate>https://jira.grc.client.com/secure/Crea ... /uricreate>
<projectkey>CINT</projectkey>
</issuetracker>

(Make sure you select JIRA soap service under the Project details and also use the Projecct key in the above config script)

And I could create Issues, access JIRA directly and open the Bug directly from Test Execution page.

I used BitNami stack to install and create the test Suite. 1.9.5 version.

Million thanks.