Error while importing from CSV

We were importing from TFS using a CSV file. We kept getting the same error at the same line. The last subject seemed to import file but did NOT properly insert the comments. The comments seem to be the last portion of an issue creation?

Here is the end of the log file:

2012-12-10 17:34:05,094 INFO - Importing issue: ExternalIssue{externalId=autoid-7044231899018060438, summary=A subject line, issueType=Sub-Task}

2012-12-10 17:34:05,147 WARN - Commenter named null not found. Creating issue with currently logged in user instead

2012-12-10 17:34:05,159 WARN - Commenter named null not found. Creating issue with currently logged in user instead

2012-12-10 17:34:05,160 WARN - Commenter named null not found. Creating issue with currently logged in user instead

2012-12-10 17:34:05,162 INFO - Importing issue: ExternalIssue{externalId=autoid-5281257600525159135, summary=A different subject line, issueType=Sub-Task}

2012-12-10 17:34:05,229 WARN - Commenter named null not found. Creating issue with currently logged in user instead

2012-12-10 17:34:05,229 WARN - Commenter named null not found. Creating issue with currently logged in user instead

2012-12-10 17:34:05,230 WARN - Commenter named null not found. Creating issue with currently logged in user instead

2012-12-10 17:34:05,232 INFO - Importing issue: ExternalIssue{externalId=autoid-1367656030117402415, summary=The last imported subject line, issueType=Sub-Task}

2012-12-10 17:34:05,284 INFO - ------------------------------

2012-12-10 17:34:05,284 INFO - Finished Importing : Issues

2012-12-10 17:34:05,284 INFO - ------------------------------

2012-12-10 17:34:05,284 ERROR - Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state

java.lang.NullPointerException

2012-12-10 17:34:05,311 INFO - Reindexing last 46 issues imported ...

2012-12-10 17:34:06,331 INFO - Reindexing took 1020 ms.

1 answer

1 accepted

Accepted Answer
0 votes

In the project we were using, there was a select list custom field. That custom field was open to all projects, but not open to all issue types. We opened it to include all issue type and we were able to import.

This could have been mitigated by having a screen that contained all imported fields or by having atlassian further open the error codes/causes during import.

As per Ivan Tse [Atlassian], this should be resolved by https://jira.atlassian.com/browse/JRA-25967

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

24,361 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you