Inflectra Customer Forums: JiraDataSynch - Spira uses old ID references from Jira (Thread) We are trying to set up a 1 to 1 relationship between Spira and Jira. But after doing so, we still get synch errors through the audit log, and some cases are reported with several different ID reference errors. And I think the error is on Spira side when trying to do the synch, that it fetches the old ID reference. So if I have a Story in Jira, and change it into a Spike, we get error in Spira audit log; Unable to locate mapping entry for issue type Spike (ID=10001) in SpiraTeam project PR# Which is a Story ID reference, when it should have been Spike (ID=10053) ref. image below from the JiraDataSynch app. 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/2506.aspxthreadId=2506Roar Holte (holte@shoreline.no)jiradatasynchJiraDataSynch - Spira uses old ID references from Jira We are trying to set up a 1 to 1 relationship between Spira and Jira. But after doing so, we still get synch errors through the audit log, and some cases are reported with several different ID reference errors. And I think the error is on Spira side when trying to do the synch, that it fetches the old ID reference. So if I have a Story in Jira, and change it into a Spike, we get error in Spira audit log; Unable to locate mapping entry for issue type Spike (ID=10001) in SpiraTeam project PR# Which is a Story ID reference, when it should have been Spike (ID=10053) ref. image below from the JiraDataSynch app. Mon, 20 Sep 2021 07:32:15 -04002025-02-11T13:54:14-05:00/Support/Forum/integrations/bug-trackers/2506.aspxmessageId=4140David J (adam.sandman+support@inflectra.com) Please could you log a support ticket for this. That way we can provide direct support. In genera Please could you log a support ticket for this. That way we can provide direct support. In general that specific error message: Unable to locate mapping entry for issue type Spike (ID=10001) in SpiraTeam project PR# Is because Jira is telling the sync that it has an issue of type Spike with that ID. The ID coming from Jira. Mon, 20 Sep 2021 10:40:18 -04002021-09-20T10:40:18-04:00/Support/Forum/integrations/bug-trackers/2506.aspx#reply4140