Jira CSV imported - issues created does not match number visible in project

[Vicky Blease]

Morning all!

I'm trying to migrate issues between two instances of Jira using the CSV importer.

I've mapped the fields successfully and in my import log I see the following confirmation of 448 issues created at the end of the file:

What's interesting is if I create an 'All Issues' queue, or indeed use search to list all issues for the project I've imported to, I can only see 245 not the expected 448.

With no errors in my import log I'm not sure how to identify these missing issues? Were they imported and I can't see them, or have they disappeared into the ether? Has anyone else experienced this?

Thank you!

Vicky

[Vicky Blease · Accepted solution]

Think I've figured this out so sharing here for other's future ref.

My import contained issues from a number of projects, consider the following example of issue keys:

PROJ1-1

PROJ1-2

PROJ1-3

PROJ2-1

PROJ3-1

PROJ3-2

PROJ3-3

PROJ3-4

Whats happening on the import, is the string value of this key is ignored and the records are merged on the integer value. Using the above example, there would be 4 successful imported records - PROJ3-1/2/3/4.

PROJ1-1 would become PROJ2-1 which would then become PROJ3-1 and so on.

[Vicky Blease]

After reading this post - https://community.atlassian.com/t5/Jira-Software-questions/CSV-Import-Results-in-Issues-Not-Existing/qaq-p/619404 - I can confirm I'm running this import as admin so I don't believe security is the problem, but I will investigate...