Your Journey to Atlassian Jira Cloud with Zephyr Squad
Greetings community, Surely by now, most of you are aware of Atlassian’s shift in strategy to become a cloud-first company. This has some important implications to anyone who uses their Server based products, including apps. TL;DR: Follow these steps to migrate your Zephyr Squad app data using JCMA: Follow Atlassian's guide to setup theJCMA Followour Cloud migration guide to complete the migration Key dates per Atlassian’s FAQ page: February 2, 2021 – Atlassian customers can no longer purchase or request a quote for new Server licenses. February 2, 2022 – you will no longer be able to upgrade or downgrade user tiers for your Server products or apps (with some exceptions) February 2, 2023 – Existing customers can no longer purchase Server apps on the Marketplace February 2, 2024 – Atlassian stops support for Server products and apps What does this mean for Zephyr Squad customers? From my calls with some of you, and what I keep hearing from our support team, is that many of you are already actively exploring your options. While some are choosing to stick with on-prem by moving to Data Center, many of you are making plans to migrate everything to Cloud, including apps. Here at SmartBear, we are committed to facilitating a smooth transition to Cloud for all our customers. This includes brining feature parity between Server and Cloud products, supporting automated migration tools like JCMA, and be compliant with a number of Atlassian Cloud security and reliability programs on the Marketplace. What is the recommended migration path to Cloud? Atlassian’s Jira Cloud Migration Assistant (JCMA) is your primary path to Cloud. It is an application that helps you move projects, users, and groups from Jira Core or Jira Software on Server to Cloud.The automated app migration functionality in JCMA is now in an open beta, which means that all users can migrate their app data over to Cloud. Are there any feature differences between Jira Server and Cloud versions of Zephyr Squad? If you want to move to the Cloud version of Zephyr Squad, it’s worth considering feature differences from Server. We’ve created a handy Server/DC vs Cloud comparison matrix where you can review these differences in detail. Are there any limitations regarding what data I can migrate using JCMA tool? Yes. Because of feature differences between the Server and Cloud versions of the Zephyr Squad, some data will not be migrated. Please refer to the ‘Known issues and limitations’ section of the Cloud Migration Guide. Are there any alternatives to using JCMA? Yes.Zephyr Migration Tool by SmartBear is another solution for migrating Zephyr Squad data from Jira Server to Jira Cloud. This approach is recommended if JCMA isn't working for you, and your Jira instance is middle-sized with a few projects, as this migration utility can migrate Zephyr Squad data only for one project at a time. What if I need any help with the migration? If you require technical assistance, please check out the Cloud Migration FAQ or raise a ticket with our support team. Tell us a bit about your Cloud migration journey I’ll conclude this post with a question to you, our awesome community. What is your plan of action around migrations? Please spend a moment to fill our this short survey to let us know!
Is there a quick way to migrate Zephyr Squad test results to another project in Jira Cloud?
I know this has been asked more than I few times. I want to move all of the test cases and results from one Jira cloud project to another, preserving the linked data between the test cases and their execution results. Can it be done and is there an easy way to do it?
Zephyr Test execution reindex failed:errorType":"ERROR","clientMessage":"We encountered some problem
Hi All, We recently came across this problem post successful migration from Jira server to Jira cloud with Zephyr App data. While following documentation for app data migration there is one step mentioned that you need to clear server cache from Zephyr configuration and perform Metadata reindex and Execution reindex. Metadata reindex works fine for migrated project while Execution Execution failing with below error: errorType":"ERROR","clientMessage":"We encountered some problems during processing this request. Please try again!","errorCode":111}" We have spent hours to figure out the issue and finally after comparing the project already exists which we can successful Execution reindex, cross verified the permission schemes for both project and identified the differences missing the addon role in migrated project, just add the role to permissions Administer project ,edit issues, browse permissions and solved the problem. Hope this will help those who struggle on last step during migration journey from server to cloud! If you still face issues let me know will try to help!Reindex Failed For Test execution: errorType":"ERROR","clientMessage":"We encountered some problems"
Hi All, We recently came across this problem post successful migration from Jira server to Jira cloud with Zephyr App data. While following documentation for app data migration there is one step mentioned that you need to clear server cache from Zephyr configuration and perform Metadata reindex and Execution reindex. Metadata reindex works fine for migrated project while Execution Execution failing with below error: errorType":"ERROR","clientMessage":"We encountered some problems during processing this request. Please try again!","errorCode":111}" We have spent hours to figure out the issue and finally after comparing the project already exists which we can successful Execution reindex, cross verified the permission schemes for both project and identified the differences missing the addon role in migrated project, just add the role to permissions Administer project ,edit issues, browse permissions and solved the problem. Hope this will help those who struggle on last step during migration journey from server to cloud! If you still face issues let me know will try to help!
