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; } } }

CSV re-import to fix dates

Steven Sproat

I've been given a CSV export of an existing JIRA project that we had in another cloud application, have set up my own JIRA cloud instance and imported this CSV in. However, I got the date format incorrect and all the tickets have not mapped correctly with the dates.

Can I re-import the exact same CSV file, with the date format correctly set and have this update the existing tasks (that have been imported in) and not create new ones?

I think the date being wrong has messed up the comment import too, i.e. all comments are like this:

Steven Sproat23 hours ago

29/03/17 6:16 AM;StevenS;all good

Or will doing this import all the comments into the issues again?

Is it perhaps better to delete all issues and to then perform the reimport? I'd prefer not to do this, as it imported all my project's releases, but didn't flag them as released and put a "release date" against it, which I had to manually do for 25+ releases.

Thanks

Accepted answers

Prakhar Srivastav {Appfire}

@Steven Sproat

If you provide issue key as field while importing the csv then it will update the existing issue and you will not need to delete them.

Check Update existing issues in the below documentation link :

https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html

Regards

Prakhar

All comments

Prakhar Srivastav {Appfire}

@Steven Sproat

If you provide issue key as field while importing the csv then it will update the existing issue and you will not need to delete them.

Check Update existing issues in the below documentation link :

https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html

Regards

Prakhar

Steven Sproat

Hi,

Thanks for the reply.

I've ran it through but keep hitting this error,

282 of 282 issues have been skipped because they already exist in destination projects.

Could this be because JIRA has changed all my issue keys from what's provided in the CSV? I had a mixture of keys in the CSV and it looks like JIRA has consolidated them all into my new project key

Prakhar Srivastav {Appfire}

@Steven Sproat

You should provide the issue key that are present in your jira system (where you are going to import ) right now.

That is the way for jira to find your issue and update it.

Regards

Prakhar

Steven Sproat

ah I was concered that'd be the case, that means having to go and cross-reference nearly 300 keys back and forth....I'll not bother and just live with it.

Thanks for your assistance.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud