Import User Picker from CSV using User Name instead of UserID

[Hendrix_ Jonathan]

I'm testing Issue import from CSV in Jira Cloud and all works well except any User Picker (Single User) custom field only seems to work if I include the UserID in the field rather than the User Name.  I've tried the User Names with quotes and without.  Tried email as well.  In every test the file fails to import due to the user not being recognized in the system unless use the full UserID for that field.  Works every time using that.  

I'm testing the import to eventually have users doing quarterly imports of a lot of issues and would like for them to not have to track down a UserID for each of these fields.  Is there a trick to importing with the User Name value?  Thanks!

Example Error: 

Issue can't be created due to the error/s [ User 'Bob Example' was not found in the system.; User 'Bob.Example' was not found in the system.; User 'Bob.Example@example.com' was not found in the system.; User '"Bob Example"' does not exist. ]

[Bill Sheboy · Accepted solution]

Hi @Hendrix_ Jonathan -- Welcome to the Atlassian Community!

I just recreated that symptom: tried an import with Assignee from an email address and it worked correctly for me with Jira Cloud, and failed on a user custom field with the error the user does not exist.

I do not see an open defect for this in the public backlog so I recommend working with your site admin to submit a ticket to Atlassian Support to learn what they suggest: https://support.atlassian.com/contact/#/

The only work-around I can think of would be to capture the user/account id list in another spreadsheet tab, lookup the account id in your import-data tab, and use that for the import.  There may also be a marketplace addon to make this work.

Kind regards,
Bill

[Hendrix_ Jonathan]

Thank you @Bill Sheboy  Appreciate the confirmation.  Will do on the ticket and good suggestion on the tabs.  I think we can work with something like that in the meantime.  

[Earl McCutcheon]

Howdy Y'all,

@Hendrix_ Jonathan  was able to reach out to our support portal, and I wanted to relay the information here to make sure that anyone else that sees this behavior knows what's up.

This behavior is a BUG that we are tracking here:
- https://jira.atlassian.com/browse/MIG-745

Currently, the only workarounds are to either use the full UserID for custom fields as noted by Jonathan or to use the external system CSV import option located under:

• Jira settings > System > External System Import > CSV Import

The External system import will allow you to use the email address of a user but it can only be completed by users with global admin, and would not be possible for end-users to complete, unfortunately, so a full account id would be required for end-users using the bulk create an option in the issue navigator.

Make sure to add yourself as a watcher on the bug report to get updates on a roll-out of the fix

Regards,
Earl