Can I import dependency links from csv file without knowing the issue key ahead of time?

[Philip Culver]

I have hundreds of epics that need to be created, and they will all contain the exact same tasks, aside from the Description title. (We have to do the same work for hundreds of customers). 

I thought that creating a csv file with the fields I need imported would be the best way to do this. I am running into an issue where I can't set up dependency links on the tasks in the csv file, because I'm importing the csv files into existing Projects in JIRA, which other teams in our company also use. So, I won't know the issue key for each task ahead of time. 

Is there any way to set dependency links based on the rows in the csv file, or something like that? I tried, but got errors during the import. 

Any other JIRA Masters have a better idea on how to accomplish this task? 

Thanks in advance!

[Petter Gonçalves]

Hello Philip.

Thank you for contacting Atlassian Community.

I understand that you are trying to import Epics in an existing project and link some tasks to it, however, once you don't have the issue key of the tasks, you would like to link the tasks using another common field value like Summary, for example. Is that correct? 

If that's the option you are looking for, I believe the Automation for JIRA plugin can help you achieve this goal. You would configure a rule like the one below:

Just to let you know how this rule would work:

- When you create the Epic issue, the rule will check if this issue is an EPIC

- Once it confirms it, the rule will find all the tasks in your site which has a specific value in the summary field and link it to issue that triggered the rule

Of course, you can use any other fields to find the related tasks you want to link and also perform any other kinds of links to the trigger issue.

Please, let me know if this information helps you.