Assignee broken when bulk importing from CSV

[Deleted user]

Starting yesterday, I noticed bulk uploading issues with an assignee listed has started giving the error "Issue can't be created due to the error/s [User '...' does not exist.] with a number that looks like maybe a GUID as the username.

This is using their username as we have done in the past. I've seen several posts indicating Jira cloud will be deprecating usernames but no reference to what to use instead when importing issues.

I tried also using an email address and @ handle as listed in the users' details page, both give the same error.

Any idea what might be going on? Is there a new identifier to use in this case instead of a username or email?

[Jon Rick]

The best "workaround" I could figure out was to leave the assignee blank and reassign the ticket after important.

[Deleted user]

Dang, yeah, this is what we've been doing as well since the problem started but it's a pain with large batches of issues. Thank you though!

[Brant Schroeder]

Faye,

  You will need to use the Atlassian Account ID. The easiest way I've found to find my accountId is to click on my icon on the sidebar and then on the "Profile" link. In the URL you can find your accountId after the last "/" :

https://********.atlassian.net/people/XXXXXX

You can find information about imports here: https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html

[Jon Rick]

Yeah, this doesn't work for me or anyone on my team :(

[Deleted user]

This doesn't work for me either.

It seems like it is correctly associating the ID number with account names, but not recognizing them. When using the old usernames it shows the correct ID in the error text, but gives the same error weather I use the number, handle, email, usename or the full [name|~accountid:numbers] as it corrects to when tagging a person in a comment.

[DPKJ]

This is seems like regression in Jira cloud.

You need contact Atlassian support for this.