JIRA CSV import: setup field mappings: many fields not available for mapping

I am moving issues between two identical JIRA instances on different servers. These instances have the same structure, Projects, etc. 

From the first instance I exported issues created after a certain date from a single project to a CSV file. I am now attempting to import that CSV into the other instance, into the same Project.

I am following the instructions in this document . I selected the CSV file and set the appropriate settings. I do not have an existing configuration for this process, so I'm going through all the steps to set it up. In Setup project mappings (step 7 of the section Running the CSV file import wizard) I chose "Select my Project" and chose the right one from the dropdown list (Note: The Wizard has no section for E-mail suffix for New Users as is listed in the instruction document).

During Setup field mappings (step 9 of the section Running the CSV file import wizard) , many (most, actually) of the fields exported are not listed in the JIRA Field column dropdown selector (for example, Attachment, Comment, Issue Key, Project Key, etc.). Of course, without this mapping, the importer won't import this information.

How can I force the Import Wizard to list the correct fields for the Project's issues?


2 answers

Did you get any responses?  I'm finding that our users don't have the same fields available to them as the admins do when using "External System Import".  This is tedious as they have to send all info to our admins for import/update.

I am having the same problem, and they are important fields like Comment Body.

I am having the same issue. I am specifically looking at loading new features/ stories, and need to link to design documents in confluence. I am missing a field mapping for "attachments" using the instructions linked above by John G.

Hi Mary,

No, I haven't had any response. I have determined the problem is that JIRA exports only those fields common to all issues selected. That is, if you have multiple issues with different field sets, JIRA will not export those fields which don't match.

Two (tedious) workarounds: 

  • Export issues by type (in my case issues of each type have the same field set)
  • Export using a binary search method – pull halves until something "breaks", then divide that half into halves and try to export each half.

Hope this helps!


I don't think this is the case, as i am able to see the fields when importing the exact same file as others who cannot search for field.  Wierd.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

883 views 5 18
Read article

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