Sync rules error: "No issue link type with name 'Causes' found.."

General Questions
,
1

Hello,

I’m receiving the following error in our jira exalate. There is no ‘Causes’ in our script, either incoming or outgoing, nor is ‘Causes’ a field in either the incoming or outgoing jira. Can someone please help?

  • Impact: ISSUE

  • Local entity: null

  • Remote entity: NBCU-569

  • Connection: tmtinsights_to_unknown

  • Error type: Sync rules error

  • Error Creation Time: Oct 09, 2025 19:29:42

  • Error Detail Message: No issue link type with name ‘Causes’ found..

  • Error Stack Trace: com.exalate.api.exception.script.IssueTrackerScriptException: No issue link type with name ‘Causes’ found.. at com.exalate.error.services.ScriptExceptionCategoryService.$anonfun$categorizeProcessorAndIssueTrackerExceptionsIntoScriptExceptions$1(ScriptExceptionCategoryService.scala:43) at com.exalate.error.services.ScriptExceptionCategoryService.$anonfun$categorizeProcessorAndIssueTrackerExceptionsIntoScriptExceptions$1$adapted(ScriptExceptionCategoryService.scala:38) at scala.collection.immutable.List.foreach(List.scala:333) at com.exalate.error.services.ScriptExceptionCategoryService.categorizeProcessorAndIssueTrackerExceptionsIntoScriptExceptions(ScriptExceptionCategoryService.scala:38) at com.exalate.processor.ExalateProcessor.executeProcessor(ExalateProcessor.java:77) at com.exalate.replication.services.processor.CreateIssueProcessor.$anonfun$executeScriptRules$1(CreateIssueProcessor.scala:221) at scala.util.Try$.apply(Try.scala:210) at com.exalate.replication.services.processor.CreateIssueProcessor.executeScriptRules(CreateIssueProcessor.scala:213) at com.exalate.replication.services.processor.CreateIssueProcessor.$anonfun$createIssue$1(CreateIssueProcessor.scala:119) at scala.concurrent.impl.Promise$Transformation.run(Promise.scala:470) at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:63) at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:100) at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18) at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:94) at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:100) at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:49) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:48) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) Caused by: javax.script.ScriptException: javax.script.ScriptException: com.exalate.domain.exception.issuetracker.TrackerRestException: No issue link type with name ‘Causes’ found.. at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.eval(GroovyScriptEngineImpl.java:164) at java.scripting/javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:262) at com.exalate.processor.ExalateProcessor.execute(ExalateProcessor.java:114) at com.exalate.processor.ExalateProcessor.executeProcessor(ExalateProcessor.java:75) … 17 more Caused by: javax.script.ScriptException: com.exalate.domain.exception.issuetracker.TrackerRestException: No issue link type with name ‘Causes’ found.. at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.eval(GroovyScriptEngineImpl.java:334) at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.eval(GroovyScriptEngineImpl.java:161) … 20 more Caused by: com.exalate.domain.exception.issuetracker.TrackerRestException: No issue link type with name ‘Causes’ found.. at jcloudnode.services.jcloud.transport.JCloudRestErrorHandlingService$.handleTrackerHigherFourZeroZeroRestResponse(JCloudRestErrorHandlingService.scala:135) at jcloudnode.services.jcloud.transport.JCloudRestErrorHandlingService$.handleTrackerFourZeroZeroAndHigherRestResponse(JCloudRestErrorHandlingService.scala:115) at jcloudnode.services.jcloud.transport.JCloudRestErrorHandlingService$.filterTrackerRestErrorResponse(JCloudRestErrorHandlingService.scala:95) at jcloudnode.services.jcloud.transport.JCloudClient.$anonfun$createIssueLink$3(JCloudClient.scala:621) … 13 more

2

The error message “No issue link type with name ‘Causes’ found” in your Jira Exalate sync usually means that the sync script (either incoming or outgoing) is trying to create or reference an issue link of type “Causes,” but that link type doesn’t exist in your Jira instance.

Even if you don’t see “Causes” explicitly in your scripts, it’s possible that:

  • The default sync scripts reference issue links (like issueLinkType = "Causes").
  • A previous customization or a template is using it.
  • The remote side is sending a link type that your Jira doesn’t recognize.

Here’s how you can resolve this:

  1. Check your sync scripts:
    Look for any lines that reference issueLinkType or issueLink.name. Even if “Causes” isn’t in your custom code, it might be in the default or commented-out sections.
    Example:

    issue.links.each { issueLink ->
    if (issueLink.issueLinkType == "Causes") {
        // some logic
    }
}

  2. Check your Jira issue link types:
    In Jira, go to Jira Administration > Issues > Issue Linking and see if “Causes” exists. If not, you can either:

    • Add a new link type called “Causes” (with an appropriate inward/outward description), or
    • Update your sync scripts to use an existing link type.

  3. Check the remote side:
    If you’re syncing with another Jira instance, the remote side might be sending a link type your Jira doesn’t have. Coordinate with the remote admin to align link types or handle unknown types in your scripts.

  4. Update your scripts to handle missing link types:
    You can add a check in your script to skip or map unknown link types to something that exists in your Jira.

For more details, see the Exalate documentation on syncing issue links in Jira.

Once you align the link types or adjust your scripts, the error should disappear.

3

Hi @Kristie

I would like to know if you are still getting this error, seems looks related to the previous error you were having when I asked you to open a support ticket.

If yes, let me know and I will assist you.

Looking forward to your answer.

Best,
Kevin

4

Hi Kevin,

Yes, still getting this error.

Thanks,

Kristie

5

Hi @Kristie

I sent you a DM.

Looking forward to your update there.

Best,
Kevin

6

Hi @Kristie

Hope this message finds you well.

I just wanted to leave an update on the thread

We found out that the error was being caused by the issue link type on the remote side. We notice that when linking a workItem using “Causes“ on the replica there was /t, meaning that the after the name causes there was a tab.

After removing the tab from workItem configuration on the Jcloud menu. The error went away and Exalate was able to sync everything as expected.

Sincerely,
Kevin

2 Likes