Importing in .csv stories with epic reference

[Alessandra Vita]

Dear community,

I am struggling with .csv import to import stories on a Jira Cloud - team managed project. I am able to create stories or task but not to have them linked to an existing epic. 

Tried to export .csv to be sure of the structure and it seems it needs to be mapped against "Parent" field, but when importing the file no Parent field is found within the mapping. Only available one from the dropdown is related to subtaks so not relevant

Also tried with Epic, Epic link with no success

Anyone experienced the same?

Thanks in advance!

[Ste Wright]

Hi @Alessandra Vita 

Is this a Team-managed or Company-managed Project?

Company-managed should work via Epic Link, but this isn't possible in Team-managed yet unfortunately, see JSWCLOUD-17758 

But I found a workaround using Automation for Team-managed!

---

Setup:

• Create a custom field - Short text (plain text only)
• For the sake of the rule below, I've used the field name "Epic Key"

Automation Rule:

• Trigger: Issue Created
• Action: Edit Issue
  • More Options (Additional Fields)
    • {"fields":{"parent":{"key":"{{issue.Epic Key}}"}}}

CSV Import:

• Create a column for Epic Key
• Add the relevant existing Epic key into it per row
• Map the field as usual when importing

---

A few notes...

• In simple terms, the rule locates the Epic Key, and enters it as the parent after the import
• It does require the key to be exact/correct

Let us know if this helps :)

Ste