Need assistance with importing Feature Issuetypes in JIRA via CSV

[Lou Gonzalez]

Our team recently procured JIRA Datacenter 9.14. We have not received formal training but have done a lot of reading and googling and have sucessfully imported Epics, but are having trouble with importing Features linked to those Epics. We consistently receive import errors that say there is an issue with either the Epic Name or Epic Link.

Our file headers are as follows:

Custom Field 1 -> custom field
Component -> component (already added to JIRA)
Epic-> Epic Link (epics already imported into JIRA. Example Epic: ABC. Import file has ABC in the Epic column)
Custom Field 2 -> custom field
Issue Type-> Feature
Summary-> Summary
Custom Field 3-> custom field

All data shown above is importing fine except for the Epic. 

These are the errors we receive:

when attempting to map the Epic column -> Epic Link in JIRA...

     Cannot add values to CustomField Epic Link in issue with summary "xyz". Exception message: cannot invoke "java.lang.long.longValue" because schemedid is null.

when attempting to map the Epic column -> Epic Name in JIRA...

     Cannot set value for locked custom field Epic Name in issue "xyz" becasue its not applicable for Issuetype 'Feature'.

Any help in creating the associating between the Epic and feature via import would be greatly appreciated. Thank you!

[John Funk]

Hi Lou - Welcome to the Atlassian Community!

The Epic Name and Epic Link fields have been deprecated. You should use the Parent field instead of the Epic Link field. 

Is the Feature a child under the Epic? 

[Lou Gonzalez]

Oh... had no idea that Epic Name/Link was depracated.

So how should we map?

Epic-> Parent Field ? And what should be in the Parent Field? The Epic name?

Currently we have Epics in JIRA that we want Features associated with. This is our vision:

Epic 1
- Feature 1
- Feature 2
- Feature 3
Epic 2
- Feature 1
- Feature 2
- Feature 3

Do we need to setup this hierarchy in JIRA first before importing?

[John Funk]

Since the Epics already exist, add a column to the CSV called Parent. Then put the issue key for the Epic in that field. It would look like:

Parent      Summary

ABC-123   Feature 1

ABC-123   Feature 2

ABC-456   Feature 3

ABC-456   Feature 4

[Lou Gonzalez]

We'll give this a try and report back. This is our first post, so its good to see how quickly people reply. Thanks so much.