nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to use new team member's name in assignee field

Shelley_Loethen

I've been using Jira since February, but haven't needed to add anyone new until now. I've added the new person to my account and also to the project. However, when I validate the CSV file before doing a bulk upload I get an error saying issues can't be created because [User 'her name' does not exist]. If I go into an existing issue, I'm able to select her name from the Assignee dropdown list.

I've checked every permission scheme, etc. but can't figure out why her issues are creating this error.

Accepted answers

Shelley_Loethen

I just received a response from Gino at Atlassian Support. Here's what he said:

"New users need to use the Atlassian ID or email in the CSV file, this is because of the GDPR compliance and we have this document with more information about why we are no longer using user names."

I wish I'd known this before I spent several hours trying to figure out what was wrong. Hoping this saves someone else some time and frustration.

All comments

John Funk

Hey Shelley,

As a quick fix, I would just upload the issues with your name. Then once those issues are created, do a Bulk change and Edit the issues to update with the new user name.

Shelley_Loethen

That's what I'm doing, but it's not going to a viable solution for long as this individual will soon have many cards that need to be uploaded.

John Funk

Just curious but why is all of this work being done in spreadsheets and not directly created in Jira?

Shelley_Loethen

We're a consulting company that works with nonprofits and are using Scrum with our grant writing team. The projects all break down into very similar parts, so we have "standard" stories (issues in Jira language) for each project. Each story gets scored by the team using agile poker based on the complexity of the specific project, but each project works through the same basic process to completion.

In 2020, we worked 180+ projects with more than 4,000 stories/issues. Excel allows us to (1) efficiently create the correct stories/issues for each project through a semi-automated process, and (2) serves as our master project calendar. Approximately every 2 weeks, prior to the start of a sprint, we create a batch of stories/issues which are then uploaded in bulk to Jira so they can be pulled into the next one or two sprints.

Shelley_Loethen

I just received a response from Gino at Atlassian Support. Here's what he said:

"New users need to use the Atlassian ID or email in the CSV file, this is because of the GDPR compliance and we have this document with more information about why we are no longer using user names."

I wish I'd known this before I spent several hours trying to figure out what was wrong. Hoping this saves someone else some time and frustration.

joao costa_0sjgk2

Yes I feel your pain. It was a rubbish idea, to do this as now JIRA does not let me search for available users when to change the Reporter - neither accept any name tat I type manually.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud