Assignee & Reporter not created when Issue is created via CSV upload

[Anjani Yadav]

Hello Experts!

I need help with Issue creation in JIRA via CSV upload. I am facing below mentioned issues:

1) Assignee is not updated via CSV i have tried e-mail-id, User name

2) Reporter is not updated as per CSV, it is always current user(person uploading the CSV file)

There is one other custom field reviewer that is working good.( able to assign person via CSV)

[Ste Wright]

Hi @Anjani Yadav 

I find User ID works well in Jira Cloud.

The User ID is the unique identifier each user's account has, and is ~40 characters long.

Three methods to locate this are:

• User Management: As a Site Admin, go to Jira Settings > User Management. Select a user - then in the URL, copy the alphanumeric phrase with dashes, etc after /users/
• People: As a user, go to People > View All People. Select a user - then in the URL, copy the alphanumeric phrase after /people/
• Issue Search: As a user, go to Filters > Advanced Issue Search. Using JQL, search for an Assignee. Select the user from the list of user options and when you "click" the name, it'll turn into the alphanumeric phrase in the search box

^ You can utilise the User ID in the upload in place of name/email, and it'll successfully locate the right user for Reporter, Assignee or a custom user picker field!

Ste

[Anjani Yadav]

Thanks Stephen for your help but it is still not working for me.

I used Issue search option to locate user ID then provided it for Assignee and Reviewer(Custom field)

Worked for Reviewer but Assignee is still blank(unassigned)

Name, E-mail id, user all three are working for reviewer but failing for assignee.

Don't Know if this is access related issue.

[Ste Wright]

Hi @Anjani Yadav 

There's a few things it could be:

• Permissions: For the project you're loading the issues into - ensure you have the permission "Assign Issues", and the users in the file have the permission "Assignable User".
• People: Related to the above, the permission scheme might provide permissions based on Project Role. Ensure you and the users in the file have the right roles assigned.
• Automation: Check there isn't an automation rule setting all created issues to Unassigned. You should be able to check this by opening one of the created issues and checking its History to see if any post-created action took place.
• Workflow Post-Function: Likewise, check there is no post-function setting the Assignee to Unassigned.

^ I'd check these out first!

Ste

[Anjani Yadav]

Thanks, I did check 2,3,4. Will check 1st as well.

For now, I have updated Assignee after CSV upload via Bulk update option.

Thanks for all the help.

[Ste Wright]

No worries :) - let us know how it goes!

Ste

[Trudy Claspill]

Note that the Reporter can be changed during CSV import only if that import is executed by a JIRA Admin by navigating to JIRA Settings > System > External System Import.

If you are using the Import Issues From CSV option that is available under the ... button on the Issue Search screen, you will not be able to set the Reporter through the CSV data, even if the operation is executed by a JIRA Admin.

[Ste Wright]

Actually Reporter and Assignee can be set via either import option.

I used the user-level importer to test the above yesterday. It should work as long as you have the appropriate permissions (i.e Modify Reporter)

Ste

[Trudy Claspill]

Hm, my mistake. Sorry to add confusion.