Hello, I followed the documentation you put online about JiraDataSync, but there is still an issue in the synchronization. In SpiraTest, the status does not update and stays stuck on New. The only way I found to change this status is to execute the workflow in Spira, which is independent of Jira. Moreover, warnings are displayed in the Event Log, showing us issues that we shouldnt encounter. For example, Unable to locate requirement mapping entry for issue type Incident (ID=10200) in SpiraTest project PR28 so setting requirement to User Story type. whereas we deactivated the requirements. Maybe youre able to see and solve the problems we encountered ? Thanks in advance for your help, Best Regards. 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/1723.aspxthreadId=1723Lucas Brun (lucas.brun@catella.lu) Hello, I followed the documentation you put online about JiraDataSync, but there is still an issue in the synchronization. In SpiraTest, the status does not update and stays stuck on New. The only way I found to change this status is to execute the workflow in Spira, which is independent of Jira. Moreover, warnings are displayed in the Event Log, showing us issues that we shouldnt encounter. For example, Unable to locate requirement mapping entry for issue type Incident (ID=10200) in SpiraTest project PR28 so setting requirement to User Story type. whereas we deactivated the requirements. Maybe youre able to see and solve the problems we encountered ? Thanks in advance for your help, Best Regards. Mon, 17 Jul 2017 13:47:19 -04002017-07-17T14:36:41-04:00/Support/Forum/integrations/bug-trackers/1723.aspxmessageId=3062David J (adam.sandman+support@inflectra.com) Hi Lucas Wed be happy to help. Please could you send this information in a support ticket to us? Thanks Adam Mon, 17 Jul 2017 14:36:40 -04002017-07-17T14:36:40-04:00/Support/Forum/integrations/bug-trackers/1723.aspx#reply3062