During the past week, batch imports which assign a ticket to a user upon creation has begun throwing an error saying "Issue can't be created due to the error/s [User ******** does not exist.]"
The imports have successfully assigned issues to the user in the past, they're still active and can see the board/project.
Anyone else running into this issue? Did something change within JIRA that might be causing this error now? How can I resolve this issue?
Thank you for reaching out.
When you say Batch Import, I understand that you are referring to CSV imports. Is it correct? Or are you importing your issues using any other method?
If you are uploading issues to an Atlassian Cloud instance, I can confirm that the way users are mapped in JIRA has changed during the last year with the removal of usernames from Atlassian Account profiles:
Right now, user picker fields (Assignee, Reporter, etc) can be mapped by:
1 - Account ID (You can check it in the user management of your JIRA instance)
2 - Email address of the user
That being said, if you are using Atlassian Cloud, check if the mapping of the email address or Account ID works for you.
If the steps above didn't work, please confirm to us if you are using JIRA Cloud or Server and provide us with more details on how you are mapping the user when importing the issue and what method/format you are using to import it.
Introducing Jira Cloud for Excel Here at the product integrations team at Atlassian, we are thrilled to announce the new Jira Cloud for Excel add-in! This add-in lets you export Jira data directly ...
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