Imported issues have incorrect statuses - all take the first status in respective workflows

[Samuel Pearce Maddox]

Imported issues have incorrect statuses - all take the first status in respective workflows

Hi,

I am unable to import the correct statuses of 845 issues using the external system import via CSV file. Each of the imported issues is set to the first status of their associated workflows in their project and do not match with the statuses in the CSV file.

I am importing the issues to our cloud instance from a server instance and have ensured that the project to which I am importing the issues has the same workflows and the same statuses. While going through the mapping steps in the import, I am mapping the Status in the CSV to the Status Jira field (not a custom field) and I am able to confirm that the statuses I am trying to map match the available statuses.

I am not getting any 'Warn's or Errors related to the statuses. The detailed log report does not show any information related to the issue status during import. All 845 issues import correctly with virtually no errors or problems (see attached screenshot - the 27 warnings were all related to users not found so attachments were associated to the currently logged in user (me)).

I have also tried updating the statuses for the issues using the external system import via CSV as documented by Atlassian, but none of the statuses changed.

Any assistance will be greatly appreciated!

Thanks,

Sam

[Vikrant Yadav · Accepted solution]

Hi @Samuel Pearce Maddox  When you select Status from dropdown and select Map field value > then Click Next . After this come back again select Status and select map field value > next > next > start import

We are doing mapping two times because first time it does pick the correct status field,in second time it pick the correct one. give it a try if it works for you.  

Thanks

[Samuel Pearce Maddox]

@Vikrant Yadav ,

The method works, though I did have to go back and forth between the Field Mapping and Mapping Field Values pages a few times before I saw that Status was actually mapping to Status and not Custom Field Status.

Thanks!

[Vikrant Yadav]

@Samuel Pearce Maddox  That's Great ....issue fixed..

Sometime jira pick custom fields during mapping ,we select the correct status field but from backend it picks custom Status field instead of System field. Just going back and mapping Status again will maps the correct status field. 

KR

Vikrant Yadav 

[Zoi Raskou]

Hi, I am sure you pay closer attention to detail than me but I will mention this for clarity. In the CSV import you can click on map values, which will then take you to a screen where you actually associate the values. The statuses do not need to be exact, you will be requested to associated each one of your old statuses with the ones available in your project. What I did wrong was that I was selecting them and moved along using the tab key. Which resulted in Jira not registering the change and mapping all the statuses in the first available. 

[Samuel Pearce Maddox]

During one of the several import attempts, I made almost an identical process to what you have described. 

I selected the Jira Field Status and checked the map fields box.

On the next screen, all of the statuses were pre-filled and matched exactly. I clicked in the first one and then tabbed through all of them so that I had actively clicked in each mapping value field. 

Then clicked import.

Are you saying I need to type out each of the statuses? I remember doing that for a couple of them just to see if by typing out a status, I would be prompted to use a 'suggested' status (though none appeared).