CSV Import Results in Issues Not Existing

[Daniel Brown]

After importing and validating the input from our CSV file, the resulting tasks don't appear to exist. We consulted the output and nothing stands out as an error. 

We're using the user-facing CSV importer, and we're running this while on an admin account. 

The output is as follows:

2017-08-03 11:32:01,390 INFO - Importer started!
2017-08-03 11:32:01,390 INFO - Engine is running in Import mode
2017-08-03 11:32:01,405 INFO - All issues will be imported to project: *********************** (KMT)
2017-08-03 11:32:01,405 INFO - Creating issue: [externalId='autoid-*********************', summary='*********************']
2017-08-03 11:32:01,483 INFO - Issue does not have issue type selected, the affected issues will be created with default issue type [Task]
2017-08-03 11:32:01,671 INFO - Issue created successfully with Key [KMT-712], [externalId='autoid-*********************', summary='*********************']
2017-08-03 11:32:01,671 INFO - Creating issue: [externalId='autoid-*********************', summary='*********************']
2017-08-03 11:32:01,671 INFO - Issue does not have issue type selected, the affected issues will be created with default issue type [Task]
2017-08-03 11:32:01,858 INFO - Issue created successfully with Key [KMT-713], [externalId='autoid-*********************', summary='*********************']
2017-08-03 11:32:01,858 INFO - Creating issue: [externalId='autoid-*********************', summary='*********************']
2017-08-03 11:32:01,858 INFO - Issue does not have issue type selected, the affected issues will be created with default issue type [Task]
2017-08-03 11:32:02,062 INFO - Issue created successfully with Key [KMT-714], [externalId='autoid-*********************', summary='*********************']
2017-08-03 11:32:02,062 INFO - Creating issue: [externalId='autoid-*********************', summary='*********************']
2017-08-03 11:32:02,062 INFO - Issue does not have issue type selected, the affected issues will be created with default issue type [Task]
2017-08-03 11:32:02,218 INFO - Issue created successfully with Key [KMT-715], [externalId='autoid-*********************', summary='*********************']
2017-08-03 11:32:02,218 INFO - Creating issue: [externalId='autoid-*********************', summary='*********************']
2017-08-03 11:32:02,233 INFO - Issue does not have issue type selected, the affected issues will be created with default issue type [Task]
2017-08-03 11:32:02,515 INFO - Issue created successfully with Key [KMT-716], [externalId='autoid-*********************', summary='*********************']

I've had to censor out the project specific information, but I don't believe any of it was relevant to the issue at hand. 

Is there a flag or something we need to set to make them accessible?

Thanks!

[Daniel Brown · Accepted solution]

Commenting again so I can close out the question.

As it turns out, our default security level was set incorrectly, and all of our imported tasks were being assigned a higher security level than any of our developers were assigned. We've reworked our security levels and the issue has been resolved. 

[Josh Steckler]

Assuming you can get into the project and see other issues there. Barring possible permissions issues, can you go to your database and see if the issues exist there?

select jiraissue.* from jiraissue left join project on jiraissue.project = project.ID where project.pkey = "KMT" and jiraissue.issuenum >= 712 order by jiraissue.issuenum;

[Daniel Brown]

Thank you for your response, Josh. We have found and fixed the issue.

As it turns out, our default security level was set incorrectly, and all of our imported tasks were being assigned a higher security level than any of our developers were assigned. We've reworked our security levels and the issue has been resolved. 

Thanks again!

[Madalina Mutihac]

Thank you for this, it took me a few hours to find the reason for this.