JIRA Integration - Which are absolute, mandatory fields?

Tuesday, June 19, 2018

When creating a new JIRA synchronization, which fields are absolutely required?

In particular, I would wish to NOT synchronize release/versions nor components. The way our JIRA projects are managed does not match up with our SpiraTest implementation and these fields serve different purposes between the two tools. I can live with components syncing, but absolutely not releases. This would balloon the information on the Releases page in SpiraTest to something large and unwieldy.

2 Replies
Wednesday, June 20, 2018
re: alburyd Tuesday, June 19, 2018


If you map Components, it will synchronize the value of a requirement or incident's component.

For Releases and Iterations, it does not synchronize the entire list, it simply synchronizes the ones that are in use by  a specific item. If you explicitly map the releases between the two systems, it will not add new ones.

For more specific recommendations, I'd raise a help desk ticket.



Wednesday, June 20, 2018
re: alburyd Tuesday, June 19, 2018

Thank you, Adam.

I simply wanted to know which fields are required when synchronizing with JIRA. In our JIRA, each build is considered a release in order to correctly track version numbers of the system. However, in SpiraTest we have a single parent release with all of the builds added through the API - so I don't really have anything in either system that could map to each other as releases go.

I will submit a help ticket when the time comes for us to set up the service.

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885


  • Started: Tuesday, June 19, 2018
  • Last Reply: Thursday, June 21, 2018
  • Replies: 2
  • Views: 8120