nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CSV to Jira Discovery Project import errors

Karthiga Sethuraj

Hello JPD team,

I get the following errors while importing ideas from a CSV file using the External System Import. I made sure I mapped them right.

1) Issue creation date is not getting imported. I get the following error.

Unable to parse created date: 5/19/2020 7:20

2) Can I import comments from two different columns in my CSV to the single comment field in the discovery project ?

3) I also get this warning for commenter field. This is not a big deal but just wondering why the importer is throwing this error.

Commenter named null not found. Creating issue with currently logged in user instead

Please advise.

Thank you,

Karthiga

Accepted answers

All comments

Jacques

Hello @Karthiga Sethuraj

I think that most of your questions are answered by going through this article, but here are a few pointers:

Months and days are usually the problem in csv interpretation. In some Jira interprets the month for a day, and in others vice-versa. For dates, I usually use the following format: yyyy-mm-dd hh:mm. For your example this would be: 2020-05-19 07:20. I also use the 24 hour format, as to not have an issue with am/pm.
Each comment column is a different comment in Jira. If you want to merge 2 comments into one, then you would need to rework your csv file (in Excel or the like) and merge the 2 columns.
The commenter field should be a user that exists in your instance. As mentioned in the article I shared at the beginning, this can either be their email address or Atlassian account id.

Hope this helps!
--- Jacques.

Rohan Swami

@Karthiga Sethuraj if @Jacques' suggestion doesn't work for you please create a support ticket for us: In the bottom left of JPD select Give feedback then Get help from the support team.

Karthiga Sethuraj

@Jacques that worked. I converted the date to a text field in the format you suggested. However I used the am/pm while converting to text.

One more question:
- Some of the custom field's content gets truncated due to exceeding the 255 character limit. Is there a workaround or solution for this ? Please advise.

Thank you for your quick response.

Jacques

Hey @Karthiga Sethuraj

It depends for which field you're trying to import this. System fields (those provided by Atlassian) can't be changed. So if they truncate there, then you'll have to actually reduce the text you want to import.

If this happens for custom fields you've created yourself, then the only solution is to (re-)create the custom field, but instead of a single line custom field, use a multi-line text custom field.

I strongly recommend NOT creating 2 different custom fields with the same name, as it only gets confusing in the long run.

Hope this helps,
--- Jacques.

Andrea McDougall

Hi, when I try to import a csv of ideas from our current solution (Aha!), I get to the field mapping step, specify which columns to map to which field, but the Next button remains deactivated and I am unable to proceed to the next step of mapping the values. Is there a relevant article for this use case? Thank you

Christopher Hogan_d5w3yc

Hi Karthiga,

The answers above should have addressed your "created date" problem. I had a similar one, whose answer may be interesting to people trying a mass import.

I was using a .csv to import a number of ideas from another application, and most already had dates for start and target completion. I did get it working, though it took some work in Excel:

I inserted two columns in the workbook that would be the import .csv, just left of my "start" and "end" columns, and named them "Project Start" and "Project Target."

The goal was to recreate the interesting date format native to JPD:

{"start":"2023-12-06","end":"2023-12-06"}

I came up with a wacky formula - but it worked:

=IF(OR(U2="",U2=0),"","{""start"":"""& "" & TEXT(U2,"yyyy-mm-dd") & "" & """,""end"":""" & "" & TEXT(U2,"yyyy-mm-dd") & "" & """}")

The goal was to check if the date field was empty or zero, and if not, to re-create the JPD string with the formatted date field included. You would need to change the column reference to match yours, obviously.

I associated the JPD "Project Start" and "Project Target" fields with these columns, and it worked the first time I tried it in production. I hope this helps.

Welcome!

It looks like you're new here. Sign in or register to get started.