Improving efficiency with pre-migration check caching in Jira Cloud Migration Assistant

Still need help?

The Atlassian Community is here for you.

Ask the community

Purpose

This article introduces a new feature in the Jira Cloud Migration Assistant that enhances the speed of pre-migration checks through caching. It reuses the results from successful pre-migration runs for identical projects to save time.

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:

  1. Data preparation error

  2. Shared Jira Service Management customer emails

  3. Invalid Jira Service Management customer emails

  4. Jira Service Management license check

  5. Jira Service Management, in cloud 

  6. Shared emails

  7. Invalid emails

  8. Jira Work Management license

  9. Group names conflict

  10. Jira license

  11. Jira in cloud site

  12. Jira Work Management in cloud

Caching of successful pre-migration runs

The results of the following two pre-migration checks are cached:

  1. Data preparation check 
    1. The Data preparation pre-migration check results are cached against a specific projectID.
    2. The pre-migration check results are saved in the AO_6FF49D_PROJ_EXPORT_PREFLT table in the DB Console.
    3. 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:

  1. To delete the entire cache: DELETE FROM public."AO_6FF49D_PROJ_EXPORT_PREFLT" WHERE 1=1 ;
  2. To delete the project specific cache: DELETE FROM public."AO_6FF49D_PROJ_EXPORT_PREFLT" WHERE "PROJECT_ID" = <ID> ;


2. Scoped Users and Groups check

    1. The Scoped Users and Groups pre-migration check results are cached against a specific projectID.
    2. The pre-migration check results are saved in the AO_6FF49D_SCOPED_USER_CACHE table in the DB Console.
    3. 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:

  1. To delete the entire cache: DELETE FROM public."AO_6FF49D_SCOPED_USER_CACHE" WHERE 1=1 ;
  2. To delete the project specific cache: DELETE FROM public."AO_6FF49D_SCOPED_USER_CACHE" WHERE "PROJECT_ID" = <ID> ;




Last modified on Apr 26, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.