How to map tasks to their related Epic using the 'Epic Link' field

Use Case
, , , ,
1

Originally asked by Kyle Jenkins on 13 July 2021 (original question)

Hello,

We are having difficulty mapping Tasks to their related Epics in the “epic link” field. Epics are exalated successfully, however, no tasks contain an “epic link” for their related Epic. Source instance is a JIRA Cloud instance and our instance is a JIRA Server instance. We’ve tried to exalate Epics first and then the Tasks but that did not work.

Can you provide the recommended approach for populating the ‘epic link’ field appropriately in our JIRA server instance? We are using a coded approach for our custom sync.

Thanks,
Kyle Jenkins

2

Answer by Ariel Aguilar on 13 July 2021

Hi Kyle,

Do you have the external script needed for Jira server? We have documentation on this, but yes you are right Epics should be synched first. Then, if you try “Exalating” a task within this Epic from Jira Cloud, you should be able to see, it got created under the Epic, in Jira Server.

Here is the document, I am suggesting:

https://docs.idalko.com/exalate/x/oAF1Aw

Kind regards,

Ariel

Comments:

Vinay commented on 30 May 2022

I tried as per the document but it is not working as expected. We are not seeing the epic link when the parent is epic and child is task.

Caroline Vandenplas commented on 04 August 2022

I have the same issue

Mitesh Sharma commented on 14 November 2022

I have the same issue.

I believe below document is about how to sync Epic JIRA it self.

https://docs.idalko.com/exalate/x/oAF1Aw

But there is no documentation on how to get the epic link field for a normal JIRA sync.