I'm using JIRA 4.3.4. I'm attempting to import a CSV file into an existing project. I'm not importing many issues with too many columns ( 3 issues and 5 fields/columns). I've mapped the fields to the JIRA fields and when I begin the import, JIRA produces the following msg:
2011-07-26 09:19:34,447 WARN - Issue ExternalIssue{summary=null, issueType=12} has a blank summary. This is being ignored. 2011-07-26 09:19:34,447 WARN - Issue ExternalIssue{summary=null, issueType=12} has a blank summary. This is being ignored. 2011-07-26 09:19:34,448 WARN - Issue ExternalIssue{summary=null, issueType=12} has a blank summary. This is being ignored. 2011-07-26 09:19:34,452 INFO - Importing with ImportBeanType: com.atlassian.jira.plugins.importer.imports.csv.CsvDataBean
the rest of the log is not pertinent.
The file looks like this:
Summary,Paragraph,Components,Comment Body,Issue Type,Priority
The system shall provide means to take a picture of a face for facial analysis,1.1.1,2. Engineering,This traces to 1.1 Photo Capture. Para 1.1.1.,Requirements,Major
The system shall provide the capability to take and store multiple pictures,1.1.2,2. Engineering,This traces to 1.1 Photo Capture. Para 1.1.2.,Requirements,Major
The system shall provide the capability to review existing pictures,1.1.3,2. Engineering,This traces to 1.1 Photo Capture. Para 1.1.3.,Requirements,Major
Have you ticked the "map" flag next to the summary? You must not do that (it's only valid for data that is going into select type fields - i.e. not text, numbers or dates)
Import completed with 3 errors:
I am getting this error can someone help me with this please. I am Admin system import option
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Actually you probably faced this bug in JIRA Importers plugin.
I agree that UI could be misleading. We are now working on making it simpler and more error-proof (e.g. allowing to mark this checkbox only for certain field types where manual mapping makes sense - i.e. there is some underlying set/dictionary of possible values)
Cheers,
Wojtek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nic, thanks for the 'hint'. I was 'checking' the box for "Additional map field value" during the issue field mapping step. That apparently was the issue. When I didn't 'check' the box, the import of the CSV file was successful.
When should the box be checked? For enumerated field types? You say that the map box should be checked only when trying to populate select field types. I assume that is for fields that have enumerated types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Betsy,
The summary field of the imported file is not empty. That is what is so frustrating about the problem. I'm sure there is something not kosher with the import file but the error message is not providing me with information to help me narrow down my issue.
I did as you said, quote my summary field, and it's still giving me the same error. My input file is as I have in the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Summary field is a required field and it can't be empty even if the project to which you're importing your issues doesn't care to use it. You can set it to a constant/junk value in the import, if you like.
FYI: You may need to enclose the string in quotes if the string value could contain commas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.