Hi, Currently we are trying to integrate the standalone spiratest tool with Jira. We are trying to handle following flow but get stuck when trying to sync the bug incident "relates to" requirement association Start condition (config) : JiraData sync plugin is used, jira user stories are imported as requirements, jira key id is also stored in spiratest, Custom 5 field in JiraDataSycn plugin is refering to Relates issue link type. 1) create user story in jira -> OK 2) sync plugin will import user story into spiratest as requirement (not as incident!) -> OK 3) once requirement is created in spiratest , we create testcases , test runs + make associations with relevant user story -> OK 4) At some point in time we start with test execution resulting in creating issues. When creating issues , issues are also associated to the relevant user story. -> Ok Next our goal (and this is were we get stuck) is to make the 'relates to' link between the spiratest requirement (= jira user story) and spiratest bug incident (= jira bug issue) also visible in JIRA (jira user story is "related to" jira bug). Everything seems to work fine as long as user stories are defined as req incidents in spiratest. In that way we noticed that when you have an association between spiratest incidents , a jira "relates to" link is also created between relevant jira issue instances. However when we try to do the same with spiratest requirements and associated bug incidents, the link between the relevant jira issues is not created (in jira). Does any one have an idea of what we are doing wrong (setup?) or is this just not feasible? Maybe some workaround? thx 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/681.aspxthreadId=681Nico Janssens (nico.janssens@persgroep.be)jira Hi, Currently we are trying to integrate the standalone spiratest tool with Jira. We are trying to handle following flow but get stuck when trying to sync the bug incident "relates to" requirement association Start condition (config) : JiraData sync plugin is used, jira user stories are imported as requirements, jira key id is also stored in spiratest, Custom 5 field in JiraDataSycn plugin is refering to Relates issue link type. 1) create user story in jira -> OK 2) sync plugin will import user story into spiratest as requirement (not as incident!) -> OK 3) once requirement is created in spiratest , we create testcases , test runs + make associations with relevant user story -> OK 4) At some point in time we start with test execution resulting in creating issues. When creating issues , issues are also associated to the relevant user story. -> Ok Next our goal (and this is were we get stuck) is to make the 'relates to' link between the spiratest requirement (= jira user story) and spiratest bug incident (= jira bug issue) also visible in JIRA (jira user story is "related to" jira bug). Everything seems to work fine as long as user stories are defined as req incidents in spiratest. In that way we noticed that when you have an association between spiratest incidents , a jira "relates to" link is also created between relevant jira issue instances. However when we try to do the same with spiratest requirements and associated bug incidents, the link between the relevant jira issues is not created (in jira). Does any one have an idea of what we are doing wrong (setup?) or is this just not feasible? Maybe some workaround? thx Wed, 21 Aug 2013 09:19:04 -04002013-11-26T15:18:27-05:00/Support/Forum/spiratest/issues-questions/681.aspxmessageId=1239David J (adam.sandman+support@inflectra.com) Hi Nico I'm afraid this functionality is not currently available - the ability to have requirements imported from JIRA and their relates links then subsequently passed back to JIRA when additional incidents are logged in SpiraTest and then get synched back to JIRA. Regards Adam Wed, 21 Aug 2013 11:14:05 -04002013-08-21T11:14:05-04:00/Support/Forum/spiratest/issues-questions/681.aspx#reply1239messageId=1243Nico Janssens (nico.janssens@persgroep.be) Adam, Thanks for your reply, You say it is currently not available. Does this mean it will become available in a future version? I 've read in the forum that soon a new version will become available in which some 'requirements' changes will be included. Thanks Wed, 21 Aug 2013 12:45:42 -04002013-08-21T12:45:42-04:00/Support/Forum/spiratest/issues-questions/681.aspx#reply1243messageId=1389Pieter Grobler (pieter.grobler@momentum.co.za) Hi, We too have now moved to Jira Agile and are now also facing the same issues. I haven't linked the Jira stories/epics to SpiraTeam Requirements yet - some documentation on this would be great! Thu, 21 Nov 2013 07:25:57 -05002013-11-21T07:25:57-05:00/Support/Forum/spiratest/issues-questions/681.aspx#reply1389