Migrating a Priority Scheme takes a very long time in Jira
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Migrating a Priority Scheme in Jira takes a very long time, taking several hours to complete.
Diagnosis
After collecting thread dumps from the Jira node that is performing the migration, we can see that it's going through each issue synchronously in a single-threaded process:
Each issue with the priority scheme updated triggers an Issue Updated event, which then triggers every webhook with that issue listener in the instance.
Cause
As webhooks are synchronous processes out of the box, there's a significant processing overhead added for every issue. Thus, the migration process takes a very long time if there are a large number of issues involved.
Solution
You can enable asynchronous webhooks, as instructed on JRASERVER-71557—Asynchronous Webhooks in Jira, which should improve the performance slightly. However, as the migration task is single-threaded, it is still a slow process.
Was this helpful?