Solution for Entegration of SpiraTest and Jira

SpiraTest is cheap but powerful test management tool. It has many useful features such integration to many open source and licensed testing and issue management tools, or automation host for HP QTP, IBM Rational Functional Tester, Selenium, TestComplete, the full list can be found here. Also it has requirement management, defect management, and there is a cycle for release - test set - test case - test run, and more can be found here. Jira is also well-known issue tracking tool and it used by many organisations. By Jira, you can track and follow the work items and easily manage the works. However it doesn't have basic testing activities so if you want to create test cases and manage the testing cycle Jira is not yet enough for these  activities. Using both of the tools, SpiraTest as test management tool, and Jira, as issue tracking tool, may lead some difficulties such as raising defect from SpiraTest and creating a related issue for development in Jira requires manual efforts. Integration SpiraTest and Jira can reduce the manual effort. You can reach the integration document from the Inflectra website which is the producer of SpiraTest. In this post, I just want to clarify some difficulties.

Firstly integration does many thing but not everything. Belong to customer support of the SpiraTest, integration does the followings:
- Adds new incidents from SpiraTest > JIRA
- Adds new issues from JIRA > SpiraTest
- Updates existing issues changed in JIRA > SpiraTest
As a result, it doesn't update the changes entered from SpiraTest to Jira. So once you update an incident from SpiraTest, the same update should be made in Jira too. Even this issue, integration is still very successful solution.

Second, in Jira project, if you have custom fields you must create custom fields respectively in SpiraTest to sync every fields. Then map the custom fields with the custom variable in Jira correctly. However, if you use SpiraTest version 4.0 and Jira version 4.2 you must use component id instead of component value.  
Component Mapping
Otherwise it gives the following error:

05.06.2013 10:22ErrorData SynchronizationError Adding SpiraTest Incident to JIRA: com.atlassian.jira.rpc.exception.RemoteValidationException: {reporter=The reporter specified is not a user., components=Component/s is required.} : [] at System.Web.Services.Protocols.SoapHttpClientProtocol.Read0View Item
05.06.2013 10:22ErrorData SynchronizationError Adding SpiraTest Incident to JIRA: com.atlassian.jira.rpc.exception.RemoteValidationException: {components=Component/s is required.} : [] at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse0View Item

Third, SpiraTest must know the users of Jira otherwise datasync gives warnings about unknown user to sync then discard the sync for updated issue. To solve the problem, both of the tools should use LDAP user list. 

Last one, if you change trace logging parameters in the DataSyncService.exe.config file from "False" to "True", system event log gives more detail about the error in the system.

   <setting name="TraceLogging" serializeAs="String">


  1. Hellow... I want to sync both sistems, but I have a question.. they have this issue currently? with the version The JIRA 5.x plugin supports JIRA 5.0 or later and SpiraTeam v4.0 or later

    1. I think they solved it, check

      Use id if you have problem try component value.


Post a Comment

Popular posts from this blog

Testing WEB Sevices and Automating SOAP Services

Performance Testing on CI: Locust is running on Jenkins

Change Default Timeout and Wait Time of Capybara

Performance Testing on CI: Integration of Locust and Jenkins

Create an Alias for Interactive Console Work: Selenium and Capybara