As TestRay Cloud is a new product which was launched in Atlassian Marketplace from this year. Therefore, some of the features in Server/Data Center are not yet present in TestRay Cloud (e.g. Automation Integration).
As TestRay supports data connection cross projects, for instance, requirements issues are created in Project A while test case associations are from Project B. So to maintain such linkages, those related projects MUST be migrated together within the same migration, otherwise, those linkages (connections) will be dropped after migration.
If the default name of below TestRay entities have been modified/updated from your Jira Server/Data Center, you need rename them in TestRay Cloud to keep them same before starting migration process. You must do the same if you are using a localized version (e.g. French) of TestRay app in your Jira Server/Data Center.
TestRay issue types: Test Case; Test Plan; Defect and Requirement. You can rename them from: Settings->Issues->Issue types
Test Run Status: Passed, Failed, Blocked, Not Tested, Not Applicable. You can rename them from: Settings->Apps->Test Run Status (only existing ones need to be updated, the rest will be created by migration automatically).
Phase 1: Migrate Data from Jira Server/DC End
Launch 'Migration Assistant home' page by following Atlassian official JCMA documentation, and then do following TestRay app specific settings along with other Atlassian recommended settings.
1. ASSESS YOUR APPS
Set TestRay app as 'Need in cloud':
2. PREPARE YOUR APPS
Make sure TestRay app is installed in destination cloud site:
3. MIGRATE YOUR DATA
Create a new migration.
In 'Choose your migration options' screen, set following:
3.1: Advanced Roadmaps plans (if have):All: 0 plan
3.2: Projects:Select all intended projects with TestRay app enabled:
3.3: Users and groups: select 'All users and groups from the Jira directory'
4. RUN MIGRATION
Once above steps are done, RUN the migration, it will takes mins to hours based on how much data you are going to migrate.
Wait until app migration progress reaches between 48% ~50% (minimum 48%), you are good to go Phase 2 now.
Phase 2: Migrate Data from Jira Cloud End
Make sure app migration progress reaches 50% before starting following steps.
1. Update 'Global Settings'
TestRay Issues: select issue types those are configured for source projects
TestRay Projects: select projects those are migrated from Jira Server/DC in Phase 1, 3.2
2. Execute 'Data Integrity' check on ALL projects those are migrated
If you have multiple projects migrated, you need do the same for each of them.
3. Execute migration from TestRay 'Data Migration' screen
After migration is started from TestRay Cloud side, you can go back to Jira Server/DC side to check app migration progress.
Wait several seconds, then refresh the page from browser, you will see migration progress in the page. If it reaches to 100%, congratulations! You data migration is successfully done!
You can now check the migrated data in your Jira Cloud.
4. Check and confirm migrated data, then click 'Acknowledge' from TestRay 'Data Migration' screen
If the data migration through JCMA is failed due to any reason, we highly recommend you trying it again. As required by JCMA, make sure the corresponding projects are deleted from Jira Cloud. If the issue
persists, please raise a ticket in our support portal, our support team will reach out and assist you as soon as possible.
Temporary Files Created in Jira Server
During the data migration, there are temporary files created in your Jira server. Those files hold all TestRay related data (e.g. Test Runs, Test Steps etc.). We recommend you zip these files and backup them for several weeks, in case to check any data migration issues.
Those files are stored in the following path in your Jira server: <JIRA_HOME>/application-data/jira/export/migration