You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, our team is doing a Jira Server to Jira Cloud migration as well as for Xray server to Xray cloud. We didn't have any issues with the Jira Cloud, however, for Xray cloud we the following issues:
1) Test Plans/Test Executions – Previous test execution results are not migrated to jira/xray cloud.
2) Test Coverage per user story links are also not migrated but the test cases were displayed under the “Issue Links” section on the user story/bug.
3) All of the test cases steps are not migrated.
Since Xray cloud now has new issue types, I have re-mapped our old issues types to the new ones but still have these issues.
There is a toolset available at XpandIt GihHub https://github.com/Xray-App/xray-cloud-mig which I was able to successfully use to move data from Server to Cloud. There are some prerequisites but in general it works.
The major issue is the performance, because there are limitations on Atlassian and XpandIt (Azure?) infrastructure sides.
I used them and was able to migrate successfully several month ago, yet there were few bugs in the code.
One of them is that names with double quotes were not migrated (tests, plans, etc.)
Other problem was in "xray_syncTestExecWithTests.py" at the line with code
responseForUser = requests.get('' + GLOBAL_onCloudMig+'rest/api/3/user/search?query='
the URL must be not 'rest…' but '/rest…'
Finally don't forger to use "-export" and "-ignore" options when running these scripts and make sure to run them in proper sequence (it is documented in their readme file).
Hope this helps.
The code which wraps the data into the message packet is not the best, so yeah, there might be issues with some cases, e.g. is email address contains apostrophes, quotes, etc. I did not face this problem with email address, but it is the same as I had with item names with double-quotes.
Xray is integrated into the Jira Cloud Migration Assistant (JCMA), and there is Early Adopters Program (EAP) already started.
Please file your application for the EAP [here|https://surveys.atlassian.com/jfe/form/SV_6SAs9OX0eAbGk5f].
Rogério Paiva [Xray Support Team]
Currently, Xray does not yet support the Jira Cloud Migration Assistant. We plan to provide this integration in early 2021.
To fill this gap until the integration is released our team created some scripts that can help you migrate your data.
These scripts are written in Python and are using the Xray REST and GraphQL APIs to fetch the Xray information from Xray Server/DC, and then import this information into Xray Cloud.
The scripts will not create new issues in Jira Cloud. The Xray issues must have already been migrated. Therefore, you first need to migrate the issues using the:
They will fill the gaps, namely:
If you face any difficulties later on, feel free to reach out to our support.
For updates on the Jira Cloud Migration Assistant integration please keep an eye on this page.
Solution Architect and Testing Advocate @Xray
Personal blog on testing, Agile, and software development: https://sergiofreire.com
Follow me on Twitter: https://twitter.com/darktelecom
Hi @Tran Tien dung ,
the python scripts update Xray related data.
The custom fields you may have on the issues (e.g. Test, Test Execution, etc) they should have been imported using the Cloud migration assistant ...
I'd recommend to reach out to our support to see if the team can help you somehow.
Note: the team is already working in a more clean process to make this migration; I don't have a timeline for it but it should happen in the short term.
Im having signifcant issues with Syncing Test Execs with Tests - commented on GitHub
Also the Test coverage panel does not update in Stories and Epics - why is that?
It worked for me in a pilot migration, but not as part of my wider migration
Heres what I did
Moved to cloud using CMA
reindexed every project within the project xray settings
switched on test coverage for stories and epics
ran scripts for Cucumber, Generic and Manual descirptions, Preconditions, Linking Pre conditions &Sets & Plans to Tests
Could you please help?
Hi @Mamta Kalwani ,
I think the best is to reach out to our support to see if the team can help you; I think something is missing there, namely going to each project settings and enable the coverage for the story and epic issue types.
Meanwhile we released Xray v4.3 with preliminary support for built-in migration (without those scripts).
More info on that here.
I just migrate Xray by JCMA, but after Jira migration, I did not see Xray migration start, there is not migrateion process as mentioned in documentation. Finally, I checked some Jira stories, I did not see any Xray data.
Do you know how I can see the migration process as below?
It is necessary to sign up for the EAP.
This is the procedure for a while, probably until the end of the year.
Atlassian manages the EAP, and during the EAP phase, they will keep an eye on the process to make sure the migration is successful.
Without the EAP, only Jira data is migrated, the Xray data (or any other marketplace App) will not be migrated.
Rogério Paiva [Xray Support Team]
I already did, here's our thread: https://jira.xpand-it.com/servicedesk/customer/portal/2/SUPPORT-24148
Really looking forward for single procedure feature for Xray project migration to Cloud. Hope this feature will be available soon.
@Joshua Rivera - I've shared your post with a few people at Xpand-IT, makers of the Xray Test Management for Jira app. We are working on improving the migration experience by making it easier to migrate apps. I'd love to connect with you on your migration experience so far if you'd be willing to chat. (I'm a product manager here at Atlassian working on the Cloud Migration Assistants and App Migrations).
If you're willing, here's how to get in contact with me.
Would you mind sharing how you migrated your core data? Did you migrate using site backup / restore or did you use the cloud migration assistants?