How to sync the Parent Link field between 2 Jira On-Premise instances?

General Questions
1

Hi Everyone,

We are working on a Jira DC to Jira DC integration using Exalate, including Epics, Stories, Bugs, Tasks, etc. We have successfully configured the sync for the Epic Link field from Source to Target. However, we are facing an issue when syncing an Epic from Target back to Source. Specifically, the Parent Link field is mandatory on the Source system, and because it’s not synced from Target, the synchronization fails and gets blocked.

The use case involves syncing the Parent Link field at the Epic level from one side to the other. Has anyone successfully handled a similar scenario where a mandatory Parent Link field needs to be synced in a bi-directional setup?

What would be the recommended approach or best practices to resolve this issue?

Thanks, Dhiren

2

@sonalig

Can you replace these lines of code:

if(replica.issueType.name == "Epic")
{
  def parentlinkIssue = com.atlassian.jira.component.ComponentAccessor.issueManager.getIssueObject("SYNCJPMMRDS-17")
  issue.customFields."10019".value = parentlinkIssue
  //debug.error(""+parentlinkIssue)
}

with

if(replica.issueType.name == "Epic")
{
  def parentlinkIssue = com.atlassian.jira.component.ComponentAccessor.issueManager.getIssueObject("SYNCJPMMRDS-17")
def hubIssue = nodeHelper.nodeHubObjectConverter.getHubIssue(parentlinkIssue)
    

  issue.customFields."10019".value = hubIssue
  //debug.error(""+parentlinkIssue)
}

Waiting for your update!

Thanks,

Sonal

3

HI

I tried the above and still getting the same error

Exalate has problems while trying to create an issue in this Jira. Details: Error occurred while creating issue. This could be due to a plugin being incompatible with this version of JIRA. For more details please consult the logs, and see: Upgrading Workflow Plugins for JIRA 3.2 | Atlassian Support | Atlassian Documentation - class com.exalate.basic.domain.hubobject.v1.BasicHubIssue cannot be cast to class com.atlassian.rm.jpo.env.issues.SimpleIssueAttributes (com.exalate.basic.domain.hubobject.v1.BasicHubIssue is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @4bea4e37; com.atlassian.rm.jpo.env.issues.SimpleIssueAttributes is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @1944a304)

4

Hi @sonalig

May i please get the update, are you still facing the issue?

Thanks,

Sonal