Cannot import CSV file

[Susan Dao]

Hi,

I cannot import CSV file. It notified: 

Issue can't be created due to the error/s [ User '5c60f8de2cdb124474b3dc96' does not exist. ]

But I still see user ID  5c60f8de2cdb124474b3dc96 on the system. And before, I still have imported successfully. 

Please help me to check this issue. Thanks

[Petter Gonçalves]

Hello Susan,

Thank you for your answer.

Please, check the following details:

1 - Check if the user you are trying to add to the assignee field is added to the Assignable user permission under Project Settings > Permissions. If you are not a project Admin, ask the responsible person to do it for you.

2 - Check if you have the global permission to Browse Users under JIRA Settings > System > Global Permissions. If you are not an Admin, as him to check it for you.

3 - Check if you are able to add this user using as the assignee of any issues in the project by using the user interface.

4 - Can you let us know if the project you are trying to import the issue is Classic or Next-Gen?

Please, let us know your results as soon as you have the chance to do it.

[Susan Dao]

Hi Petter,

Thank you for your reply. 

Unfortunately, I tried again with Account ID; e-mail address and username, but all of them still error. In file CSV, i set name column as 'Assignee' and mapping with 'Assignee' on Jira. 

I attached an example:

[Petter Gonçalves]

Hello Susan,

Thank you for reaching out.

I believe you are mapping the user picker fields in your CSV file with the Account ID instead of the Username. Is it correct?

In fact, Atlassian is currently removing the username field from JIRA profiles, however, specifying usernames in CSV exports for JIRA Cloud is still supported in the short term, while mapping user Account ID was not possible due to the following bug:

Importing CSV where user custom fields are specified by account ID or email does not work

That being said, the fix for the mentioned bug was implemented yesterday. Can you check if you are able to map the User Picker field with the Account ID or e-mail address now?

If the above suggestion doesn't work, can you try with the username? There's a possibility that the fix has not been rolled out for all Cloud instances yet.