The main requirement for this use case is to maintain the issue hierarchy while Exalating issues between Jira and ServiceNow (bi-directionally).


The Epic → Task relationship must be reflected as Change Request → Incident relationship on ServiceNow, and vice versa. The following depicts what we are trying to achieve here:

Let us first consider the Jira to ServiceNow side:


Let us now consider the ServiceNow to Jira direction:


The entire code from the Jira side is here, and for ServiceNow is here


Please review the following video to see the use case in action: