Jira crashing when selecting cross-project boards and filters in JCMA

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Learn what to do when the Jira Cloud Migration Assistant (JCMA) app crashes Jira when selecting to migrate cross-project boards and filters.

Overview

When choosing the data to migrate and scoping cross-project boards and filters, Jira becomes unresponsive and needs to be restarted.

Checking the atlassian-jira.log, you can see the below error and error stack:

atlassian-jira.log

1 2 3 4 5 6 7 8 9 10 11 12 ERROR .... /rest/migration/latest/check/plan/<mig_plan> [jira.migration.utils.CompletableFutureUtil] Execution Exception occurred while fetching future java.util.concurrent.ExecutionException: java.lang.StackOverflowError at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191) ... at com.jtricks.function.links.LinkedAllIssuesFunction.getLinkedIssues(Unknown Source) at com.jtricks.function.links.LinkedAllIssuesFunction.a(Unknown Source) at com.jtricks.function.links.LinkedAllIssuesFunction.a(Unknown Source) at com.jtricks.function.links.LinkedAllIssuesFunction.a(Unknown Source) at com.jtricks.function.links.LinkedAllIssuesFunction.a(Unknown Source) at com.jtricks.function.links.LinkedAllIssuesFunction.a(Unknown Source) at com.jtricks.function.links.LinkedAllIssuesFunction.a(Unknown Source)

There is a recursive call to the LinkedAllIssuesFunction.a() function that ends in a StackOverflowError.

This function belongs to the JQL Tricks Plugin.

Solution

If the third-party app is being used in Jira On-Premise, contact app vendor support.

If the app is no longer used in Jira On-Premise, remove its functions from the filter's JQLs to resolve the error.

Updated on April 17, 2025

Still need help?

The Atlassian Community is here for you.