Import and Link Epic with tasks while NOT using Epic Name as Epic Link

[Duane Cronkite]

It appears you can have multiple issues with the same "Epic Name" so... how do you import and link Epics with tasks while NOT using Epic Name as Epic Link?

[AhmadDanial]

Hi, Duane.

When discussing about matters between these 2 fields, I would like to share the Epic Name vs Epic Link KB that is written that explains the definition of them and how they are being used in JIRA.

In your case, linking Epics with tasks should take into consideration the Epic Link instead of Epic Name instead since Epic Link is the relational link to determine an issue's parent epic and available to all issue types. However, do take note of this:

 Starting in JIRA Agile 6.2.2 or in any version of JIRA Software, if you add the Epic Link field as a column in your JIRA Issue Navigator, it will display the actual name of the epic (Epic Name) rather than the issue key of the epic.

May I know if you have any specific use cases that you can more details on to provide clarity on this?