Currently, if an app server listener can't be found for a 3rd party app, the JCMA tool skips that app from that migration plan without notifying the user through UI.

This led to confusion post-migration, and the customer reached out to Atlassian Support for clarification. Also, the customer has to re-run the Migration, which can cause unexpected delays in their migration schedule window.

Current Behaviour

The only indication is a warning message in the Jira application logs. Below is a snippet for the X-Ray app. But it can happen to any 3rd party app.

WARN admin /rest/migration/latest/plan/dbcf7def-XXXX-4087-XXXX-bbbf524583c9/start [c.a.j.migration.execution.MigrationExecutionService] com.xpandit.plugins.xray has an automated path but is missing a server listener. This app will be ignored during app migration.

Ideal Behaviour

The Admin/User running the migration should be notified of such behaviour through JCMA UI, especially before executing a migration, so the customer can make informed decisions about the migration and plan it accordingly.