Imported via csv external import into production after testing in dev and test, but discovered issue!

We ran a csv import of issues into an existing production used project and discovered a problem. The csv file incorrectly put the assignee/reporter to the full name; for example, Alex Karpow, which created a new login alexkarpow and assigned the issues to bad logins instead of for example the real login of alparow that is what we have in Microsoft AD domain controllers and is what is needed for authentication. We cannot delete the production used project or restore to a day prior to the bad csv import as a lot of new issues have gone in already. Do you have any way for us to fix this issue--in that, change the reporter/assignees in bulk to the correct logins? This is affecting production project work.

2 answers

This widget could not be displayed.

JIRA Command Line Interface can always be used in situations like this if bulk edit doesn't handle the situation for some reason. Use updateIssue action together with one of the run actions like runFromIssueList

This widget could not be displayed.

Maybe you should have a look in another question How can I use the Groovy Runner jira user id rename form the command line?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

137 views 1 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you