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

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

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Sunday in Agility

You asked for it, so we delivered: images on issues have arrived

A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...

732 views 3 11
Read article

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