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 re-import a stopped import.

Derek White_hupbic

Using old importer.

Started an import.

Hit stop after it got a few issues imported.

When I try to re-start the import by going through the whole process again with the same CSV, same config file uploaded, and same options selected, it doesn't even try to import and simply takes me back to the "stopped" screen:

0 projects and 8 work items imported successfully!

Stopped by user admin. All objects already imported have been retained. Data may be in an inconsistent state.

The logs linked are the old logs.

Edit:

I tried importing from a new tab - same result.
I tried renaming the CSV file - same result.
I tried changing line endings in an attempt to change checksum of file - same result.
I tried removing already imported rows without linked issues from the CSV - same result.
Seems like the project is locked?!

Accepted answers

Derek White_hupbic

Deleted the imported issues and then it let me re-import.

I guess it won't update existing issues, at least not after a stopped import.

All comments

Derek White_hupbic

Deleted the imported issues and then it let me re-import.

I guess it won't update existing issues, at least not after a stopped import.

Chand Bhardwaj

I am facing the same issue. Tickets were not even created, so can't delete. any suggestions?

Sathish_zffmfh

I too got the same issue, after tried below options it worked for me.
1) First clear/delete tasks from JIRA

2) rename import csv file with different name (try to keep different text in initial part of file)

Aaron Holesgrove Sr_

I ran into this problem too. Here's how I solved it.

Firstly, I was doing imports using an existing configuration file. I stopped an import manually whilst it was happening and then couldn't do another one afterwards - whilst continuing to keep trying to use the same config file along with a csv of records to import.

The solution was to not only rename the csv file that had the import records in it, but to not use an existing configuration file at all. That meant for that one time, I had to manually specify all of the columns to fields mappings again but the import worked. I saved that config file for future use and didn't use the same name of the old config file that I was uploading and then I could do future imports using that config file just fine.

THAT fixed it and got me importing again. Hope this helps anyone out there.

Charlie Misonne

I retried with a different file name, different config file, no config file, another user on another PC. None of it works.

When creating a support ticket with Atlassian it tells me about this bug https://jira.atlassian.com/browse/JRACLOUD-81962

I'm still waiting for Atlassian's reply to unblock us. If there is anything helpful I will share it on this thread.

Aaron Holesgrove Sr_

Hmm interesting. Thanks for sharing that bug report. I didn't experience that - when I stopped my import, it didn't upload every record, only what had been imported up until that point (You'd think something like an import would be wrapped in a transaction to roll back what was imported so far if you hit stop during the import, right?).

I guess the reality is that we're all trying to diagnose how to work around a feature that's defective and that the best explanation is that the feature needs intervention from Atlassian. You can't solve gremlins yourself.

I suspect the solution will ultimately be that the new import tool will be able to eventually work with existing Jira projects when that feature is added and that the old import tool that we're all talking about will be switched off. Currently they're offering both and we're all struggling with the old import tool.

Charlie Misonne

Hi Aaron

Indeed I think the CSV import feature is not the best. I've been using it since years (mainly on server/ DC) and the userinterface has not changed. Not sure about the backend though.

About my issue: in the end it resolved itself after a few hours (night). And we were able to run th eimport on our production import without similar issues.

Atlassian could not pinpoint our issue. The tips we got are: stay on the import screen while it's importing (which we did) and start with smaller batches.

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