<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Jira 4 Spiratest 3.2 Integration issue working with Jira components (Thread)</title><description>&#xD;
 G'Day Spiratest Gurus,  I&#xD;
 am the Jira administrator and not really experienced spiratest user &#xD;
however I was given the task of the integration of these products. So, &#xD;
after following the documentation, I have spiratest v3.2 and Jira v4.2 &#xD;
integrated this way:  2 spiratest projects to the same Jira project but to two different components  Spiratest stream 1     Jira Project A Component 1 Spiratest stream 2   Jira Project A Component 2   It works fine in the Jira side (issues created in Spiratest gets mapped in the right component in Jira and do not get duplicated)  No so good  in the spiratest side for issues created in spiratest in one stream (gets mapped right in Jira) but gets duplicated in the other stream also the Jira project A has more than 2 components and when an issue is created in different components still gets mapped in both streams of spiratest (with blank component) .  Is there a way to avoid duplicate issue in spiratest? or the only way is to map the two streams to two different Jira projects  Cheers Carlos        Warm regards Carlos  &#xD;
&#xD;
</description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spiratest/issues-questions/429.aspx</link><item><guid isPermaLink="false">threadId=429</guid><author>Carlos Reyes (carlos.reyes@utas.edu.au)</author><title>Jira 4 Spiratest 3.2 Integration issue working with Jira components</title><description>&#xD;
 G'Day Spiratest Gurus,  I&#xD;
 am the Jira administrator and not really experienced spiratest user &#xD;
however I was given the task of the integration of these products. So, &#xD;
after following the documentation, I have spiratest v3.2 and Jira v4.2 &#xD;
integrated this way:  2 spiratest projects to the same Jira project but to two different components  Spiratest stream 1     Jira Project A Component 1 Spiratest stream 2   Jira Project A Component 2   It works fine in the Jira side (issues created in Spiratest gets mapped in the right component in Jira and do not get duplicated)  No so good  in the spiratest side for issues created in spiratest in one stream (gets mapped right in Jira) but gets duplicated in the other stream also the Jira project A has more than 2 components and when an issue is created in different components still gets mapped in both streams of spiratest (with blank component) .  Is there a way to avoid duplicate issue in spiratest? or the only way is to map the two streams to two different Jira projects  Cheers Carlos        Warm regards Carlos  &#xD;
&#xD;
</description><pubDate>Thu, 15 Nov 2012 06:11:21 -0500</pubDate><a10:updated>2013-10-09T08:34:40-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/429.aspx</link></item><item><guid isPermaLink="false">messageId=815</guid><author>David J (adam.sandman+support@inflectra.com)</author><title>&#xD;
&#xD;
&#xD;
Hi Carlos Unfortunately we only recommend (and support) mapping one SpiraTest project to one J</title><description>&#xD;
&#xD;
&#xD;
Hi Carlos Unfortunately we only recommend (and support) mapping one SpiraTest project to one JIRA project. The components in JIRA should get mapped to a custom property field in SpiraTest rather than to try and map to multiple projects.  Regards  Adam </description><pubDate>Thu, 15 Nov 2012 20:01:55 -0500</pubDate><a10:updated>2012-11-15T20:01:55-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/429.aspx#reply815</link></item><item><guid isPermaLink="false">messageId=817</guid><author>Carlos Reyes (carlos.reyes@utas.edu.au)</author><title>Thanks Adam for the quick reply, now to convince my client that he has to create 3 Jira projects so </title><description>Thanks Adam for the quick reply, now to convince my client that he has to create 3 Jira projects so it can be mapped to their equivalent 3 Spiratest ones Cheers Carlos &#xD;
&#xD;
</description><pubDate>Thu, 15 Nov 2012 21:23:35 -0500</pubDate><a10:updated>2012-11-15T21:23:35-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/429.aspx#reply817</link></item><item><guid isPermaLink="false">messageId=1324</guid><author>Pieter Grobler (pieter.grobler@momentum.co.za)</author><title>&#xD;
  Adam (Support)  &#xD;
&#xD;
&#xD;
Hi Carlos Unfortunately we only recommend (and support) mapping one SpiraT</title><description>&#xD;
  Adam (Support)  &#xD;
&#xD;
&#xD;
Hi Carlos Unfortunately we only recommend (and support) mapping one SpiraTest project to one JIRA project. The components in JIRA should get mapped to a custom property field in SpiraTest rather than to try and map to multiple projects.  Regards  Adam   Good day,     Can you please confirm if this one-to-one relation is also/still applicable for SpiraTeam 4.0 and Jira 5?     Regards  Pieter &#xD;
&#xD;
</description><pubDate>Wed, 09 Oct 2013 08:34:40 -0400</pubDate><a10:updated>2013-10-09T08:34:40-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/429.aspx#reply1324</link></item></channel></rss>