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. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiratest/issues-questions/1868.aspxthreadId=1868Dimitri Albury (Dimitri.Albury@keenfinity-group.com)jira integration releases components 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. Tue, 19 Jun 2018 20:24:32 -04002018-06-21T18:47:56-04:00/Support/Forum/spiratest/issues-questions/1868.aspxmessageId=3318David J (adam.sandman+support@inflectra.com) Hi If you map Components, it will synchronize the value of a requirement or incidents 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, Id raise a help desk ticket. Regards Adam Wed, 20 Jun 2018 06:48:40 -04002018-06-20T06:48:40-04:00/Support/Forum/spiratest/issues-questions/1868.aspx#reply3318messageId=3320Dimitri Albury (Dimitri.Albury@keenfinity-group.com) 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 dont 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. Wed, 20 Jun 2018 12:43:26 -04002018-06-20T12:43:26-04:00/Support/Forum/spiratest/issues-questions/1868.aspx#reply3320