Import Issues with different reporter

[minki kim]

Hi, 

when using import issue, can we put a different reporter?

When I tried with different reporter, the ticket is still created with my name. 

[Mikael Sandberg]

Yes, that is possible, but the user has to exist on your instance and you have to use their email address. You can find more information about how to prepare your csv file here.

[Minki.Kim]

@Mikael Sandberg thank you

I did try with email address, and its user does exist.

Looking at your link, it appears it requires user id?

Where can i get that?

[Mikael Sandberg]

You can get it by either go to Teams and lookup the user, the account Id is the last part of the URL for their profile. You can also go to admin.atlassian.com > Product > Users and search for the user there.

[Minki.Kim]

sorry @Mikael Sandberg  you are right, email can do as well. However, I tried both email and account ID, but both failed. Could it be something to do with Jira admin setup?

[Mikael Sandberg]

Are you mapping the the field when doing the import?

[Mikael Sandberg]

And I would recommend that you check the box for Map field value, it will then tell you if the user is being correctly mapped for the first line in the csv.

[Minki.Kim]

I did

It sounds silly but is there any letter limit, like long name ?

[Mikael Sandberg]

Did the detailed log show any errors? Does the users have access to the project?

[Minki.Kim]

There was no error message. Yes, the user have access. 

In fact, that user's role is set as Production Users. 

Should I set it to Project role?

[Mikael Sandberg]

Yes, try and add them, at least temporarily, to the modify reporter permission, just to see if that makes a difference.

[Minki.Kim]

no luck, that does not do anything... 

[Minki.Kim]

noticed that reporter cannot be edited. How can we change the setup?