Cannot map to Project Key using External System Import / csv

[Katie Averill]

Up until today, we have been able to map to the project key field when importing / updating issues through the admin portal (External System Import / csv) function.

When I try to select project key as the mapped Jira field, it tells me that the value is invalid.

As I'm trying to update issues across multiple projects, my understanding is that project key is a required field per:  https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html 

Is this a bug - or something unique to data center (which we recently switched to this week).

[Joshua Sneed _ Contegix · Accepted solution]

Hi Katie,

It might be a bug, but could be any number of things. First, review the logs and Troubleshooting & support to see if the app is complaining about proxy/ssl/gadget feed/etc. Atlassian apps like to talk to themselves through their API and incorrect configuration gets in the way of that.

Second, verify you have appropriate permissions in all projects in the CSV. Alternatively, break the import down by project and perform multiple imports.

You should also check out https://jira.atlassian.com/browse/JRASERVER-65981, which lightly points to trailing spaces. Check the project names and your CSV for 'formatting' errors like trailing spaces.

Cheers,

JS

[Katie Averill]

Thank you - I was able to identify an error in my import that was creating the issue.  I appreciate the quick reply!