CSV bulk upload in JIRA

Manali Butey_74pgd2

I am in the process of setting up a JIRA project for my team . Whilst I get setup I need to circulate a template to the team so they can start populating and I can use it later to bulk upload all to JIRA.  2 questions on the columns for bulk upload:
1. assignee field - should the team be populating the username / full name / email address of an existing user in JIRA?

2. Plan to create the epic -> feature -> user story -> task hierarchy. I understand that i will need an issueID, issuetype column and for the linkages I will have to have multiple columns with outward links. These outward link columns i think need to be populated with the issue ID. but cause none of these have been created in JIRA how do I know which issue ID i should start with. Also, there are multiple resources who will work separately to populate the template and should not have clashing issue ID's. Do i pick a random issue ID say 10000 and assign to one team to start, and 30000 to another team ? 
P.S there will be more columns than stated above such as summary, dates , etc. The ones stated above is where is confusion lies.

Trudy P Claspill

Hello @Manali Butey 

Here is a link to a reference document about importing from CSV.

https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html

Concerning your first question, you need to provide usernames that match to valid usernames already set up in JIRA, and those users in JIRA must have the Assignable User permission in the destination project.

With regard to your second question, concerning linking issues during import, when the issues you want to link are actually being created by the import.

The way to do that is to first create an artificial Issue ID field in your input data, and populate that with a unique value per issue. Example:

Issue ID, Issue Type, Summary
1, Epic, First Epic
2, Story, First Issue

Then you use that unique Issue ID in the field where you want to create the link. For example if you want the above story to be a child of the epic:

Issue ID, Issue Type, Summary, Epic Link
1, Epic, First Epic
2, Story, First Issue, 1

When you are mapping the fields during the import process, map the Issue ID column to the Issue Key field.

The import process will use your artificial Issue ID value to keep track of how to link the issues together. First it will import each issue, internally keeping track of the actual issue ID assigned in JIRA as the issues are created. Then it will make another pass through your import file and create the links between them.

You can indeed give each team a block of numbers to use for the artificial Issue ID when they are contributing to the import data file. You will want to double check the final file to make sure there are no accidental duplicates.