JiraDataSynch - Spira uses old ID references from Jira

Monday, September 20, 2021
Avatar

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.

1 Replies
Monday, September 20, 2021
Avatar
re: AdmiralOOM Monday, September 20, 2021

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.

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

 

Statistics
  • Started: Monday, September 20, 2021
  • Last Reply: Monday, September 20, 2021
  • Replies: 1
  • Views: 3448