When using CSV import to bulk create issues, how to import Epic(existing) and assignee field?

[CECILIA ZHENG]

When using CSV import, how to import Epic(existing) and assignee field?

Epic: Not newly created, but existing ones
What to put for assignee field? Tried user email but doesn't work.

[Trudy Claspill · Accepted solution]

Hello @CECILIA ZHENG 

Welcome to the Atlassian community.

To specify a user in a user picker field in your CSV file use either the user's login (i.e. email address) or the hexadecimal account ID assigned to the user in the Atlassian Cloud ecosystem.

To associated an imported issue with an Epic include the Epic's issue ID, and map that column to the Parent field during the import. Note that works only for Company Managed projects. It is not currently possible to make an imported issue a child of an Epic in a Team Managed project during the import process.

[CECILIA ZHENG]

Thank you Trudy! 
Question 1: Where can I find the hexadecimal account id? Tried to explore it everywhere but without any luck. Also I tried to use my email address which is my login in, but that doesn't work.

Question 2: For the Epic import, do you mean I can perform below:
CSV: Provide the Epic id only-eg, ABC-123

Then map that to jira field "parent link" instead of Epic link or Epic name field?

Thanks!!

[Trudy Claspill]

Q1: If you go to the Teams menu, search for the user, then open their record, their hexadecimal account ID will be part of the URL that is displayed.

https://yourJiraUrl/jira/people/5edebb1234548a0ab529eba0

You will have to specify users that have the Assignable User permission in the project, the Assignee field will have to be part of the Create Issue screen in the UI, and you will have to have the Assign User permission.

I tested with both my own email and my hexadecimal account ID, and both worked.

Q2: Yes, use the Epic key; i.e. ABC-123

Map that column to the Parent field, not the Parent Link field, not the Epic Link field, and not the Epic Name field.

[CECILIA ZHENG]

Thanks Trudy!

I solved the user id, for the epic, I mapped the Epic key(CSV) to Epic link field in Jira and it worked. I am using Jira server not sure if this is caused by this.

[Trudy Claspill]

Yes, use of Jira Server/DC makes a significant difference. The requirements for the CSV are different. My answer was based on the tags you added to your post indicating you were using the Cloud product and a Free subscription plan. My answers don't apply if you are actually using Jira Server/DC.