New EPIC , Task ,Bug ,Sub Task Import from csv and linking the Tasks ,Bug ,Sub Task with createdEPIC

[Marx]

I have a requirement ,some example given below


I have to create a new epic ,Bug Tasks and Sub Tasks newly and link them each other properly 

I would need a working template ,in the above what is the change i would need to do in csv file and the setting to be done in JIRA to do this import properly .Aim is to create everything one by one and link them properly .

Thanks is advance , 

For both Cloud ,Company owned data center JIRA provide help

[Lukas Nicolai_Seibert]

Hi @Marx ☺️, If you're open to using a third-party app for your cloud instance, I think Templating.app could be a good alternative to an CSV import. 

You can easily create issue templates for hierarchies epic, issue, subtask. You can also link them with each other and afterwards you can create all of them in a project with just one click: 

You can find us at the Atlassian Marketplace ➡️ https://marketplace.atlassian.com/apps/1224664 

This is how such a issue hierarchy could look like: 

[Marx]

Can anyone support working solution for this 

[Mohanraj Thangamuthu]

Hello, Good day. Please use the following format.

[Mohanraj Thangamuthu]

Confirmed on my test instance.

[Marx]

As this JIRA is in project managed and not in cloud , your given tags and my system fields not matching , tried your update ,not working , 

Few errors : Task not associated with Subtask

Epic name is required 

only Task created no EPIC created , No linking done

the modified format of the CSV is here

@Mohanraj Thangamuthu 

[Marx]

summary	Epic Name	issue type/ Work Type	issue id/ work item id	parent	assignee	Development Team
Epic with parent and no child story but 1 sub-task and parent Initiative		Epic	1		RKumar36	Other
Task	Epic with parent and no child story	Task	2	1	RKumar36	Other

[Mohanraj Thangamuthu]

To confirm, above format worked for you in Jira Datacenter version?

[Marx]

This format is not working ; Very simple EPIC to Task Linking is required after it is newly created ; Please share the template i will try the same.

[Mohanraj Thangamuthu]

Thanks. Please create a Test Epic and a child issue under the Epic. After that export both these two issues to .CSV. You will get the format that is required to import the issues as well. Let me know if these steps help.