Please make sure you have done the formatting for the date fields as outlined in the lower portion of: https://confluence.atlassian.com/display/JIRA/Importing+Data+from+CSV
There is no way for you to set the Issue Key. This is decided at the time the issue is created. You can create a custom field to store your legacy issue keys if you wish.
I was able to import all those fields successfully in a test attempt. Many more fields appeared in the drop down list, including an issue key. I deleted the project because I wanted to map values for the issue key in order to retain it from the original system I am copying it from. When I tried to import the same CSV files again I did not see a number of fields I need there anymore. I believe it is possible to retain Issue Keys (we use VTTR-nnnn format) if you check "Map field values" on the import. The project I am importing to is blank.
The only thing I played with between the import attempts is workflows which are not now applied to any of the projects. Don't know what to do.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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