Hi, Our spiratest is currently syncing with JIRA (cloud). One of the jira plugins we are using is Greenhopper which alows you to work 'Agile' (User stories, sprints, ...). We 've currently managed to import/sync the user stories from JIRA to Spiratest as requirements which is good :-) Unfortunately we have noticed that one specific user story field is not synced to spiratest -> 'Sprint' field value. This is quite bizar as Sprint field is basically a custom jira field which is mapped to a custom spiratest field. However after further investigation (I'm not a webservice export!), we 've noticed that when we get the details of an issue through the jira rest api , the response for the sprint field looks a bit different (ToString) from any other data fields (respond looks more like the JSON way) EXAMPLE: customfield_10007 :[ "com.atlassian.greenhopper.service.sprint.Sprint@a29f07[rapidViewId= ,state=CLOSED,name=NORD - Sprint 42,startDate=2013-07-29T06:47:00.000+02:00,endDate=2013-08-11T20:47:00.000+02:00,completeDate=2013-08-14T15:31:33.157+02:00,id=107]" , ,state=ACTIVE,name=NORD - Sprint 43,startDate=2013-08-14T15:32:47.322+02:00,endDate=2013-08-23T15:32:47.322+02:00,completeDate= ,id=117]">com.atlassian.greenhopper.service.sprint.Sprint@769133[rapidViewId= ,state=ACTIVE,name=NORD - Sprint 43,startDate=2013-08-14T15:32:47.322+02:00,endDate=2013-08-23T15:32:47.322+02:00,completeDate= ,id=117] ], Has anyone already faced this problem? Any solution / workaround available? thx Regards Nico 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/integrations/bug-trackers/731.aspxthreadId=731Nico Janssens (nico.janssens@persgroep.be) Hi, Our spiratest is currently syncing with JIRA (cloud). One of the jira plugins we are using is Greenhopper which alows you to work 'Agile' (User stories, sprints, ...). We 've currently managed to import/sync the user stories from JIRA to Spiratest as requirements which is good :-) Unfortunately we have noticed that one specific user story field is not synced to spiratest -> 'Sprint' field value. This is quite bizar as Sprint field is basically a custom jira field which is mapped to a custom spiratest field. However after further investigation (I'm not a webservice export!), we 've noticed that when we get the details of an issue through the jira rest api , the response for the sprint field looks a bit different (ToString) from any other data fields (respond looks more like the JSON way) EXAMPLE: customfield_10007 :[ "com.atlassian.greenhopper.service.sprint.Sprint@a29f07[rapidViewId= ,state=CLOSED,name=NORD - Sprint 42,startDate=2013-07-29T06:47:00.000+02:00,endDate=2013-08-11T20:47:00.000+02:00,completeDate=2013-08-14T15:31:33.157+02:00,id=107]" , ,state=ACTIVE,name=NORD - Sprint 43,startDate=2013-08-14T15:32:47.322+02:00,endDate=2013-08-23T15:32:47.322+02:00,completeDate= ,id=117]">com.atlassian.greenhopper.service.sprint.Sprint@769133[rapidViewId= ,state=ACTIVE,name=NORD - Sprint 43,startDate=2013-08-14T15:32:47.322+02:00,endDate=2013-08-23T15:32:47.322+02:00,completeDate= ,id=117] ], Has anyone already faced this problem? Any solution / workaround available? thx Regards Nico Wed, 09 Oct 2013 14:49:55 -04002014-08-29T09:47:47-04:00/Support/Forum/integrations/bug-trackers/731.aspxmessageId=1329David J (adam.sandman+support@inflectra.com) Hi Nico We don't currently support this special Greenhopper field. It may be added to future versions of the plugin depending on customer feedback/demand. Regards Adam Thu, 10 Oct 2013 11:25:05 -04002013-10-10T11:25:05-04:00/Support/Forum/integrations/bug-trackers/731.aspx#reply1329messageId=1802Michael Duncan (michael.duncan@ddihealth.com) Hi, Has there been any movement on this? We are using JIRA v.6.2.5 and JIRA Agile v 6.4.2(formerly Greenhopper ) and would like to sync with SpiraTest Fri, 29 Aug 2014 09:47:47 -04002014-08-29T09:47:47-04:00/Support/Forum/integrations/bug-trackers/731.aspx#reply1802