Identifying and disabling background jobs that impact migration process in Jira Data Center
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
The purpose of this document is to provide instructions on how to identify and disable background jobs running on Jira DC that may cause migrations to become stuck or slow down.
Solution
If your migration is slow due to background jobs running on your Jira instance then it is generally due to
Scheduled index snapshot that is by default setup to run every night.
Third party apps that have scheduled some background jobs.
To disable “Scheduled index snapshot” follow the below steps:
Go to Administration (⚙️) > System.
From the left-side menu, select Indexing.
On the Indexing page navigate to Scheduled index snapshot section and click Edit Settings.
Turn off the Enable index recovery and click on Update.
To identify third party apps that run background jobs and disable them follow the below steps:
Go to Administration (⚙️) > System.
From the left-side menu, select Scheduler details.
On the Scheduled administration page click on the Jobs tab.
Check for all jobs that are taking longer time to run and running too frequently using the Last run duration and Schedule columns.
The Jobs column should give you an idea about which app it job belongs to.
Disable all such apps which have jobs listed on this page. This will disable the jobs as well.
Remember to enable Scheduled index snapshot and all disabled apps after your migration is complete so that your Jira instance functions as expected.
Was this helpful?