As a site admin or org admin, I cannot map the "Status" or "Status ID" during csv bulk import

[Joe Collins]

In the past (several years ago) I was able to conduct bulk uploads and place issues in the correct status.  Today, now that we have significant complexity in our JIRA instance, I am unable to map the Status of issues in JIRA.  I have tried the project specific upload within the project.  I have also tried the global external issues import.  Neither case will allow me to map Status or Status ID.

The Atlassian documentation states that this is possible.  Does anyone know what configurations or technical debt we may have put in place over the years that is preventing this mapping?  

We are importing thousands of issues so manually moving them is not a viable option.  The only work around I can think of is adding labels and the doing a filter followed by several bulk transitions...then remove the label.

[Marc - Devoteam]

HI @Joe Collins 

Status should be simply importable. Are the Status names in the CSV equal to the status names in the workflow and are you using the correct status names related to the workflows and the issue types.

On importing check the checkbox to validate the status import.

@Manoj Gangwar Status is not a field on a screen.

[Manoj Gangwar]

Hi @Joe Collins

Please check if the status field is added to the edit screen then use the global import option.