While importing issues from a csv file, how to map old status to Jira issue status?


We are running JIRA 6.3. I am importing the issues from our old issue tracker cvstrac via a csv file, somehow during field mapping, issue status does not show up from the JIRA side to be mapped to. Thus all the imported issues end up in the "New" status. Did I miss anything here?

Could you please let me know what is the proper way to map issue status?  Any help is very much appreciated.





5 answers

1 accepted

Ahh, Chris, I think you're using the 'Import Issues from CSV' feature rather than the 'External System Import'.  You want to go to Admin -> System -> External System Import -> Import from CSV and use that tool.  The tool I think you're using is available to anyone who can do bulk updates (available from the Issues dropdown) and has limited capabilities.  The admin tool will be able to update all fields.

Status should be there as an option. I can't think of why it would be missing.

0 vote
Timothy Chin Community Champion Mar 29, 2015

Can only be mapped to existing workflow statuses in JIRA. If not specified in your CSV file, imported issues will be given the default (i.e. first) Status as specified in your JIRA system.

Source: https://confluence.atlassian.com/display/JIRA/Importing+Data+from+CSV

Thanks for your answer! I did not address the problem properly, am attaching a screen shot below.

Here is the screen shot I was referring to. On the right side - JIRA field selection, there is no "status" field to be mapped to.


Hmm. Curious. I can affirm that I've definitely mapped statuses using the CSV importer before. Are you mapping to a new project or into an existing project? I'm wondering if you need to map into an existing project for it to have a workflow to reference for statuses.

To an existing project with a workflow. And yes, back then with earlier version of Jira, I was able to import and map status, not sure what has changed.

I Am facing the same issue in JIRA v6.4.7 while Importing CSV file. Status Mapping is only done if the status is "In Progress".

Mikey please help..



Same issue here with Jira Cloud.  Status and Issue Type field not available in list of Jira fields to map into. Mikey Schott above seemed to indicate this required using External System Import, but also indicated Status field should be available in the normal bulk import tool.  this is also indicated in Atlassian support docs, which reference importing to Status field via the bulk import tool. Please advise.  thanks! 

Hi, @Bryan Pace. I'm not sure if status can be mapped using the standard user-facing bulk CSV import tool, and the current documentation on this for Cloud doesn't mention mapping of statuses: https://confluence.atlassian.com/jiracorecloud/creating-issues-using-the-csv-importer-765593817.html . This is likely to prevent users from overstepping permissions and workflow restrictions in the target project.

What is your goal for the import? Do you have access to the admin CSV importer?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,305 views 14 20
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot