Problem Summary

The notifications Migration, once started, won't stop unless the plugin is disabled. However, if the Notifications plugin is re-enabled, the job will resume, without any user intervention.

This can be undesirable for large instances, where the migration may create performance problems.

If the migration task completes as expected, this isn't a problem, but it is a problem if it runs for a long time and an administrator needs to stop it unexpectedly.

Potential Workaround

Manually unregister the migration task using the Script Console by running the following script:

import com.atlassian.sal.api.component.ComponentLocator
import com.atlassian.scheduler.SchedulerService
import com.atlassian.scheduler.config.JobRunnerKey

JobRunnerKey jobRunnerKey = JobRunnerKey.of("migrationTask")
def schedulerService = ComponentLocator.getComponent(SchedulerService)
schedulerService.unregisterJobRunner(jobRunnerKey)