1. Introduction

Inspired by our existing solution for migrating grid data from TGNG Server/Datacenter to TGNG Cloud, we’ve developed a dedicated UI within the app itself to streamline the migration process. This new feature allows you to perform migrations directly from TGNG Server/Datacenter to TGNG Cloud without relying on external tools like Script Runner.

The primary goal is to simplify the migration process by providing an intuitive interface that requires minimal input. The system will automatically handle the rest, ensuring a smooth and efficient migration. Pre-requisites include connecting to an existing cloud site, which will serve as the target for the migration.

2. Installation Instructions

• You can access this feature by upgrading to our beta release version 2.2.0 on the Atlassian Marketplace.

• Important: Before running the migration, ensure that you back up your data.

• If you experience issues or decide to revert to the stable version, simply uninstall the beta and reinstall the production release from the Atlassian Marketplace. Your data will remain intact and will not be lost in this process.

3. What’s New

• Step-by-Step Migration Process:

  • A new, detailed UI guides users through the entire migration process, explaining each step and outlining all prerequisites required for a successful migration.

• Progress Tracking

  • The migration process now features clear step indicators within the UI, allowing users to easily identify their current position in the workflow at all times.

• Simplified Authentication

  • Authentication between Jira Server/Datacenter and Jira Cloud is streamlined with a user-friendly interface, including fields for:

    • Jira Cloud site URL

    • User email for migration

    • Protected authentication tokens for both Jira Cloud and Jira Server/Datacenter.

• Improved Grid and Column Mapping

  • A dedicated UI allows users to easily map source grids from Jira Server/Datacenter to target grids in Jira Cloud. Users can select source and target grids via checkboxes and map columns with matching data types.

• Support Contact Integration

  • A direct link to the Table Grid support portal is now available, making it easy for users to ask questions or seek help during the migration process.

• Real-Time Error Notifications

  • Users can monitor live logs and view detailed error screens to diagnose issues during the migration process.

• Migration Progress Visualization

  • A progress bar is included to show real-time migration progress and provide an estimated time for completion.

• Pre-Migration Review

  • Users can now review migration details before initiating the process, ensuring they are fully informed about the actions to be taken.

Overview look

• Step 1 - Prerequisites:
  Here, you will find all the necessary information and requirements needed before proceeding with the data migration. Make sure to review this section carefully to ensure a smooth migration process.

  Open

  

   

• Step 2 - Authentication:
  This is the crucial first step, where you authenticate and connect to your target Cloud instance. Ensure that all the information you provide is accurate and follows our guidelines to avoid any connection issues.

  Open

  

   

• Step 3 - Select Grid:
  After authentication, you can now choose the grids you wish to migrate. Multiple grids can be selected at once. Additionally, you'll see useful information related to the projects and issues associated with each grid to help guide your selection.

   

   

   

• Step 4 - Mapping:
  On this screen, you will begin mapping grids from TGNG Server to the target Cloud Grid. You also have the option to select “Add new grid,” which will automatically create a new grid in the Cloud with the same configuration and data as the Server, simplifying the migration process.

   

• Step 5 - Review:
  Before the migration begins, you will have the opportunity to review your selected grids and mappings. You can go back to previous steps if adjustments are needed. Additionally, any warnings related to the grids that could impact the migration process will be displayed in the “Warning found” section, let you be noticed necessary updates before proceeding with the migration. For example, if you're migrating grids with different configurations between Server and Cloud, a warning will appear to inform you of this discrepancy, because you need to make sure grid configuration is the same between Server and Cloud.

• Step 6 - Migration Progress
  Here we go the migration run, in this screen, you can track the progress of migration by seeing the progress bar showing the percentage and also the remaining time until it finish. You can also have option to cancel the migration at any time (Please note that grids migrated before cancellation will remain on the Cloud and cannot be rolled back. Additionally, you can use the “Retry” button to continue migrating any remaining grids.)

   

   

• Step 7 - Result
  Once the migration is complete, you will be able to see detailed information, including the number of grids successfully migrated, any grids that failed to migrate, along with the specific reasons for failure. You'll also see the total execution time and overall migration status. If you have any questions, there’s a button to contact our support team. Additionally, you can download the migration log for further review if needed.

   

   

4. Guide Notes

• TGNG apps installed on both Jira Server / Datacenter and Jira Cloud instances

• All grids configuration must be manually exported from Jira Server / Datacenter instance and imported into the Jira Cloud site, or you can choose to create a new grid in the mapping screen.

• All Jira projects and issues that are using grids from the source instance must already be migrated to the target Cloud site

• All Columns in the Grid Config are made editable in the Jira Cloud site before running the script (can be changed after)

5. Send feedback/Report bug

• To provide feedback or report a bug, please utilize the Customer Portal as per usual. Kindly ensure that you include details pertaining to version 2.2.0 so we can accurately identify any issues from the 2.2.0 Library Upgrade.

• We eagerly anticipate receiving your feedback to enhance this feature and will be scheduling a brief meeting with you to discuss further.

6. Known bugs

• Grids from new projects created after installing the beta version cannot be migrated at this moment.

  • Workaround:
    After creating a new project, please restart your Jira Server. This allows the grids from the newly created projects to be migrated.

• UI/UX Concerns: we would appreciate your feedback on any specific areas of the UI/UX that may seem less user-friendly. Your input will help us make improvements before the production release.