Improving efficiency with pre-migration check caching in Jira Cloud Migration Assistant
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
This article introduces a new feature in theJira Cloud Migration Assistantthat enhances the speed of pre-migration checks through caching. It reuses the results from successful pre-migration runs for identical projects to save time.
Solution
Environment
Jira 7.6 and higher
Jira Cloud Migration Assistant version 1.11.2 or higher
Summary
The Jira Cloud Migration Assistant now enhances efficiency by caching and storing the results of successful pre-migration checks. This allows for faster pre-migration runs for migration plans with identical configurations.
However, these cached results are valid for 30 days, after which they are automatically removed.
Eligible pre-migration checks for caching
The following pre-migration checks are eligible for caching:
Data preparation error
Shared Jira Service Management customer emails
Invalid Jira Service Management customer emails
Jira Service Management license check
Jira Service Management, in cloud
Shared emails
Invalid emails
Group names conflict
Jira license
Jira in cloud site
Caching of successful pre-migration runs
The results of the following two pre-migration checks are cached:
Data preparation check
The Data preparation pre-migration check results are cached against a specific projectID.
The pre-migration check results are saved in the AO_6FF49D_PROJ_EXPORT_PREFLT table in the DB Console.
The cached results expire after 30 days, after which they are automatically removed. However, any updates to the project issues during subsequent pre-migration runs are detected, and we re-run the data preparation check for the updated issues.
To manually overwrite and run the pre-migration check again, you have two options:
To delete the entire cache: DELETE FROM public."AO_6FF49D_PROJ_EXPORT_PREFLT" WHERE 1=1 ;
To delete the project specific cache: DELETE FROM public."AO_6FF49D_PROJ_EXPORT_PREFLT" WHERE "PROJECT_ID" = <ID> ;
2. Scoped Users and Groups check
The Scoped Users and Groups pre-migration check results are cached against a specific projectID.
The pre-migration check results are saved in the AO_6FF49D_SCOPED_USER_CACHE table in the DB Console.
The cached results expire after 30 days, after which they are automatically removed. However, any updates to the project issues during subsequent pre-migration runs are detected, and we re-run the scoped users and groups check for the updated issues.
To manually overwrite and run the pre-migration check again, you have two options:
To delete the entire cache: DELETE FROM public."AO_6FF49D_SCOPED_USER_CACHE" WHERE 1=1 ;
To delete the project specific cache: DELETE FROM public."AO_6FF49D_SCOPED_USER_CACHE" WHERE "PROJECT_ID" = <ID> ;
Was this helpful?