I import batches of issues frequently from CSV files. I always set the Assignee = the Atlassian user name. But this new change has just gotten in my way:
I can no longer see the user names on the Site Admin.
Does anyone know what I set the Assignee field equal to in the CSV? Is it the Full Name? If so, does it have to be in quotes?
Hello @Ericka Samuels,
I've actually just had the same question when importing issues from CSV files. We still can see usernames in the URL: let's say you're looking at your user profile, the URL should be https://yoursitename.atlassian.net/admin/users/view?username=Ericka.Samuels
I've just checked a user created today and he also has username = firstname.lastname, so I guess Atlassian gets the portion of their email address before the "@" character as their username.
Hope this helps,
It doesn't seem like this works any more. My user profile link looks like this: https://kanasoftware.jira.com/people/4ad10d7053b99a2a7cd299bb
(I manipulated the hex string for privacy).
For the heck of it, I tried putting in that hex string as my username in the import mapping, and that didn't work either.
Update: Nevermind, this works by mapping to the prefix of the email address of the user. It seemed to default to atlassian.net addresses, but if I import from the main menu, not a project, I have the option to specify my own suffix.
When I export our Jira users to CSV there is no username field. There are fields: id, full_name, and email. I have tried all three of these values and the mapping fails. I see no way to find user names which can be used in issue import.
For some of our accounts I'm capable to find the appropriate user ID for a CSV import by usage of the auto-complete of the JIRA issue search: Typing into the search field "Assignee =" then starting to type a well-know user name will show a drop-down with accounts. Clicking on the desired user will add a user ID into the search field. This user ID worked in many cases, but not all.
Finally JIRA support solved my issue: In JIRA Cloud I was capable to access "CSV Import" by the three dots menu at the "Advanced search for issues" page without the required admin privileges (looks like a bug). After I got the admin privileges for my project and used the correct import page (accessible via 'Jira Settings' / 'System' / 'External System Import') I was capable to import and assign issues by usage of the team member mail addresses.
@Mara Finkelstein As you may be aware, there are two bulk import tools: an admin and a non-admin tool. The admin tool lets you import Assignee and Reporter, but the non-admin tool only lets you import Assignee.
Either way, when you are mapping one of your file columns to the Jira assignee/reporter field, make sure "Map field value" is checked. Then on the Map Values page, you need to map your file values to team members' full email addresses (like email@example.com). You can find the full email addresses on the User Management section of the Admin page.
Alternatively use the users' full email addresses in your input file and you won't need to map values.
@Mara Finkelstein Yes, that is the admin tool. And you can use team members email addresses in the Assignee/Reporter columns of your input file, then map those columns to the Assignee/Reporter fields in Jira. As long as the column values match the email addresses of your Jira users exactly, the bulk importer should be able to import correctly.
Foy my case I had to use the user ID in the csv, as the username was not working. With the userID it was successful. Got the userID from clicking on the user and in the url can see the id like so :
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