Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to import Assignee from CSV using Import Issues from CSV within Project?

I'm trying to create issues in a project using the Import Issues from CSV function (Filters->Advanced Issue Search). I've managed to overcome a number of issues, including using the UserID as opposed to email address to populate a custom user picker field.

While I can set other fields just fine, including Reporter (using email address) I can't seem to set the Assignee. The import validates but the Assignee is always set to "Unassigned" when the issue is created. I've tried using full email address, email prefix (before the @) and UserID but nothing works.

The ONLY way I have managed to achieve setting the Assignee is to use the External System Import method as a Jira Admin. That works fine but of course, then my notification automation rule within the project doesn't run. My question is WHY can I set the Assignee using one method and not the other? I want people within the Project to be able to regularly import issues and not rely on Jira Admins.

1 answer

1 accepted

0 votes
Answer accepted

Hi @Phillip Traynor 

You should be good to have your issue created and assigned to a user if you add the user key. I just ran a quick test and got an issue created and assigned to a user using the following CSV file:

Summary test,5b59dede106e222d95ea26aa


Here is a screenshot of the mapping:



I hope it helps, but if you are still not successful, share a screenshot of the mapping.



Thanks Alex, I stripped down my import file and still didn't have any joy - until I double-checked my Create Screen and noticed that Assignee was not a field (I probably removed it during earlier testing).

Once I added the Assignee field back to the Create Screen I was able to set the Assignee using the CSV Import, using the email address (I assume it will also work with UserID).

I'm surprised the import passed validation without the Assignee Field really being mapped to a field on the screen but I guess since it is a default field something allows it to pass.

Thanks for your help.


Like Alex likes this

Hey @Phillip Traynor 

That's a tricky one, and you nailed it. While creating issues in bulk, Jira only considers the fields available in the create screen. This indeed different from importing from external source. 

I'm glad you managed to get it working, well done!



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

👁‍🗨 Confluence Team planning dashboard_Atlympics 🌈

Hi Atlassian's, How is your journey with #Atlympics 2021 so far....excited! Me too, same excitement. Here's my typical team planning and vision dashboard which I used to share to my management and ...

25 views 1 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you