How to import a CSV file into JIRA 7.10

[Jim Malgieri]

This is actually 2 questions re: CSV import of fields into JIRA 7.10  If you think I should break this into 2 separate question, let me know.

1) DATE-TIME fields.  In the CSV file I'm importing from ,there is a TIME field and a DATE field.  I only see a DATE and a DATE-TIME field in the JIRA mappings. How do I merge the date & time fields into the DATE-TIME field? I was hoping JIRA would do this for me but it appears I need to manually merge the 2 CSV fields into a single csv field. Am I correct?

2) Our CSV file is approx 150 columns by 3,000 rows. When I tried to import the CSV file I got an error, looked it up and saw the error is a known bug in JIRA. and there is a limit on the number or rows/columns I can import at one time . . . great, just great.

Is there any general method for importing a file with this many rows & columns to make this as painless as possible?

Thank You.

[Earl McCutcheon · Accepted solution]

Hi Jim,

For your first question yes you will need to manually modify the data in your csv file so that the data and time formatting is combined into a single value, by default the time setting is looking for "dd/MMM/yy h:mm a" so today at 2pm would be "09/Jul/18 2:00 PM" but you can use an alternate format and specify the date format used in your CSV file using syntax that complies with the Java SimpleDateFormat.

i.e. if you had Military time in your CSV and today 2PM was indicated as ""09/Jul/18 14:00" you could specify "dd/MMM/yy HH:mm" for the time setting while importing the CSV.

Next the BUG you noted sounds like you are referring to this one:

• https://jira.atlassian.com/browse/JRASERVER-62597

And unfortunatly until the Bug is fixed breaking the import into smaller batches (Reducing the number of rows and/or columns) is the only option as a workaround at this time. 

I would say reduce the row count by half repeatedly until you are able to locate an optimal import volume for the Bug workaround, and save your field mapping configuration for the first import so you can use the *"Use an existing configuration file"* option on the subsequent imports this way you do not have to re-map the fields each time, as manually mapping 150 columns on each import would get pretty tedious.

Regards,
Earl

[Jim Malgieri]

thank you, Earl.  You've confirmed my assumptions and work-arounds.  This bug is really a shame, especially since it seems to have been there for quite a while.

[Earl McCutcheon]

Hi Jim,

I am glad I could help out and I wish I had a more immediate workaround for your CSV import.

Also, if you have the time to do so please leave some feedback on the Bug Report noting your specific use case and how its impacting your data migration, as covered in the  Atlassian Bug Fixing Policy, we monitor all the feedback and use this as one of the methods to help define the priority of a bug fix based on the user impact caused by the bug.

Regards,
Earl