• Products
  • Documentation
  • Resources

Xray Test Management for Jira

This page provides an overview of things you should consider when assessing and migrating your Xray Test Management for Jira app data to Cloud.

Helpful resources

General guidelines

  • Assess & plan app migration early
    Avoid assessing and planning app data migration late in your migration journey, as this can result in unexpected delays and challenges in your overall migration. If your app data is critical and required in cloud, you should plan your app migration early, along side your core Jira product migration.

  • Communicate directly and raise a support ticket with Xblend for your migration
    Contact and establish a communication channel with Xblend (the Marketplace Partner / app vendor)
    Marketplace Partners have the most knowledge about their app, and are better prepared to support your migration when they’re informed early about your migration plans, degree of data migration complexity and your specific requirements for Cloud.

    • Monitor the Xray support ticket you’ve raised, and respond in a timely manner to ticket communications. If customers are unresponsive or inactive on support tickets, Marketplace Partners may need to close support tickets.

    • We recommend informing your Marketplace Partners about:

      • your planned migration schedule (including updates about changes to your migration plans)

      • security considerations

      • the level of support you require, and

      • any other app specifics that would be valuable for them to know before you continue to install, test and migrate the app to Cloud

  • Engage an Atlassian Cloud Migration Manager (CMM)
    If you’ve engaged a CMM, we recommend using MOVE tickets for support at the earliest possible point in your migration. Inform your CMM if:

    • the migration solutions you’re recommended are not feasible to implement, or can potentially cause delays.

    • you’re unable to get the response or support you require from the Marketplace Partner.

You’re eligible to engage a CMM if you have:

  • 250 or more active users per migration, and have not engaged a Solution Partner

  • 1000 or more active users per migration, and have engaged a Solution Partner

  • Consider engaging a Solution Partner
    It is recommended that you engage a Solution Partner to assess, plan and migrate your app data. Solution Partners generally have extensive experience migrating customer data to cloud, and can help you plan ahead, foresee any risks, and offer the right strategies and solutions for migration.

  • Assess your migration complexity
    Expect a higher degree of migration complexity if you have large server/DC instances, or a highly customised instance.

  • Check for Marketplace Partner updates
    You should check for scheduled maintenance or incidents on the Marketplace Partner’s platform that can impact your app migration.

  • Check for the level of support you can expect from the Marketplace Partner for migration.

If you’re planning migrations over weekends, we strongly recommend checking if the Marketplace Partner is available to support your migration.

Planning the app migration

Before you begin, it’s important that you carefully assess and plan the app migration. This section discusses things you should consider for the app migration.

Estimating app migration time

As migration time is directly dependent on the size and complexity of your data, it’s not always possible to determine exactly how long a migration can take.

However, you could try estimating your migration time by completing test migrations before committing to any timelines. This allows you to get a rough estimate of how long your final production migration can take, and also detect any issues that can potentially arise.

Reducing (descaling) your app data

You can apply strategies to improve the speed of your future migration, particularly if you find that the migration takes a long time during your test migrations.

Descale data (reduce data size) using these options (where applicable):

  • delete historical / older data that you may not require in cloud. Reducing data can be done using Xray's REST APIs.
    However, we recommend that you engage an experienced Solution Partner to advice you on, and help execute such descaling strategies.

  • If you need to migrate files larger than 16MB, we recommend consulting Xblend and/or your Solution Partner about the best method to migrate large files.

  • starting fresh in the cloud after backing up server data.

If reducing data size is not possible for your migration requirement, or if descaling data did not reduce migration time sufficiently, contact Xblend for further options.

Preparing the migration

Upgrade to the latest version of Xray Test Management for Jira

Always upgrade to the latest Xray app version before test and production migration.

Clean up Jira data prior to migration

App data may not be stored entirely on the Jira database. Cleaning up Jira data allows you to decrease the amount of app data you need to migrate.

Ensure that all linked projects are migrated in the same migration plan

Before you run a migration, ensure that all the projects that have links to the ‘Xray Test Management for Jira’ app are included in a single migration plan.

Xblend’s migration documentation provides more information about using pre-migration checks to ensure all linked projects are included in the migration.

Complete essential manual tasks

In order to ensure a successful migration, follow the instructions provided by Xblend about essential manual tasks you need to complete before migration.

If you’re using the Migrate All At Once option in JCMA, ensure that you’ve followed the additional steps specified by Xblend .

Running the migration

Getting app migration progress updates & reports

After you have started running the migration, use progress logs of JCMA to monitor this app’s migration.

Unblocking a migration that appears stuck

If your ‘Xray Test Management for Jira’ migration appears to be stuck, it’s likely that the migration is taking longer than expected.

In such scenarios:

Before you cancel the app’s migration, we recommend reaching out to Xblend to confirm the status of your app migration. This is to ensure that you’re not canceling an app migration that actually might be progressing smoothly.

  • If your app’s status appears as Skipped in the CMA, it’s likely that the server listener of this app is not registered. We recommend that you disable and then re-enable the app to try resolving this issue.


Still need help?

The Atlassian Community is here for you.