Can't seem to map CSV into key Jira fields(status, assignee, etc)

Doug Powell October 15, 2014

I am attempting to import about 800 issues using the CSV import to Cloud Jira/Jira Agile.  I have looked at the help documentation regarding the fields I can use and how to use them, and the behavior I'm seeing from JIRA is not matching with what the documentation says, as far as I can tell.

I have created a number of custom fields, and I can map those to JIRA just fine.

Here are the fields I am having difficulty importing to Jira:

  • Date Created - Not available to map (*1)
  • Status - Not available to map (*1)
  • Assignee - Not available to map to (although my "View Field Configuration" screen shows it) (*1)
  • Project Name - Not available to map (*2)
  • Project Key - Not available to map (*2)
  • Comment - Not available to map.  I have configured my csv to contain multiple columns named Comment, so I can create several (child) comment records with my new Issue (*2)
  • Component - This field maps, but the importer will not create new values (I have over 100 components I am referring to in my issues, they all fail in in my import tests)

The help documentation I am referring to is:

https://confluence.atlassian.com/display/AOD/Creating+issues+using+the+CSV+importer

(*1) - I am doing this according to the instructions in the section Tips for importing CSV data into JIRA fields

(*2)  - I am doing this according to the instructions in the section Importing issues into multiple JIRA projects

 

Thanks in advance for the help.  I am really struggling here and welcome any sage advice.

 

 

3 answers

1 accepted

9 votes
Answer accepted
pborkowski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 15, 2014

Hello Doug,

it may be confusing, but we currently have two CSV Importers.

  1. Bulk Create - "Import issues from CSV" available under Issues top menu - this one is meant for Bulk-creating issues and is available for non-administrators. As it's exposed to such users, we had to limit available options, for example changing status.
  2. CSV Importer - "Import from external system" available from System configuration - this one is meant for import/migration use cases. It's only for administrators, so we allow here all type of fields and operations. You should use this one - you'll find here all of the fields that you have listed.

We are still working on our documentation to clearly state the differences between those features. 

 

Conor McCooey December 18, 2014

This is ridiculous. Has the documentation been updated?

Katrina Schoen September 28, 2015

Hi @Przemyslaw Borkowski , Have you added any new documentation on this issue? I'm trying to find out exactly which fields are available for the Bulk Create tool (accessed from the top menu). A number of our custom fields seem to be unavailable there, and I can't figure out if/how the options map to our JIRA permissions. I need to allow one of our non-admins to bulk upload tickets, but we're currently blocked by this problem. Any help would be greatly appreciated!

Tarun Sapra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 22, 2017

I hope this is documented soon, I was quite confused as to why some fields are missing. It's better to make sure only people with admin rights can perform this operation so that they can see all the fields.

Cristian Zara March 13, 2017

Apparently the documentation is still not present regarding the import of issues for normal users and admins.

Alec.Puype June 6, 2017

Indeed, stumbled accross the same problem.  It would have been nice if it was documented correctly.  Would save a lot of time...

Josh Strange August 14, 2017

I lost almost half a day to trying to figure out how to map the comment field (after giving up on mapping issue key which it turns out I can also do. Also the admin tool doesn't have features like validate.

Tõnu Kerge March 25, 2019

:) - 4,5 years later and it still has not been updated - wow. There should at least a warning for end users or something - strange is that bulk does not even recognize exact matched - not by Description to Description not description to description.

At least something, but no carrot this time.

TY

Like Engin Yorgancıoglu likes this
0 votes
Sakthiya Giri September 8, 2020

Oh my god when i was a fresher i read this comment and now i became a manager still reading the same and waiting for the update. 

JOSE CARLOS DIAZ GARCIA February 3, 2021

@atlassian should read this thread and the thousand more like this... Keeping unsolved this issue makes no sense in 2020... I understand that these crappy importers and their confusing documentation is directly an invitation to buy add-ons. 

0 votes
Fay Strickland February 10, 2020

Almost a year on .....  Please correct me if I am wrong but the Admin import functionality no longer appears to exist in the Administrators area.  The documentation has NOT been updated though.  Looks like its all back to square 1.    It seems that the import is possible in External System Import>CSV (Jira import) but even mapping the fields still creates new issues instead of updating existing ones, despite the Issue Key being mapped. 

Does anyone have a solution to updating existing issues in the cloud as I have spent far too long trying to get a config file that actually updates.

 

 

 

  

Noel Dinger April 1, 2020

In my Jira Server Instance (v8.5) the Import functionality "External System Import" in the system administration is still available, as well as the Bulk Importer unter the Issues Navigation Menu. 

But I could not find any documentation on it anyway.

Suggest an answer

Log in or Sign up to answer