How to move Rally Test Set and Test Cases to Jira Zephyr

[Godwin Pearl]

Hi :

We have decided to move from Rally to Jira. In Rally, currently we have solid test set and test cases and metrics / reports captured from those test set/cases.

In Jira (Zephyr), any suggestion on how to move those rally test set / cases?

Thanks for the help.

[OpsHub]

Hi @Godwin Pearl 

Migration projects are typically complex and require careful planning and strategy. The following factors should be considered before Rally to Jira Cloud migration.  

 1) Format change: Rally uses HTML for rich text formatting while Jira uses Wiki. So, you need to plan such formats conversion [Like how to convert HTML format to the wiki for the data being migrated] 

2) Sprint migration with Open State: If Sprints are being migrated, those need to be migrated with Open State until all other issue types are migrated. Finally, Sprint’s status needs to be reconciled as per Jira.  

3) Model mismatch between Rally and Jira: Zephyr allows you to retain test results of only the last Run i.e., there can be only a single Test Execution record for a given Test Case and Test Set (unlike Rally, which allows you to record the result of every Run). Zephyr would be able to absorb most of Rally Test data, other than Rally Test Results - Rally Test cases will move to Zephyr Test Case, Rally Test Plan to Zephyr Test Folders, Rally Test Set to Zephyr Test Cycle, and Rally Test Result to Zephyr Test Execution.   

4) Loss of entity context and activities: Opt for a solution that migrates the data with history to prevent loss of data. 

5) Impact on user productivity: Plan the migration in such a way that the user is able to use the system during the migration so that it does not have a negative impact on the overall organization operations.   

For migration from Rally to Jira, there are two broad approaches:  

1. Use CSV-based export, import: Only basic data (like basic fields, simple descriptions) can be migrated. This option will not preserve test data, comments, attachments, and relationships. This becomes challenging with its own limitations in terms of import of a limited number of issues and is tedious and error-prone when the size and complexity of the migration increases. 
2. Use a 3rd part migration tool: This allows a seamless transition taking care of all the above-mentioned aspects so that you can experience a smooth and rich data migration without impacting your business continuity and productivity.  

OpsHub has extensive experience in undertaking complex migration projects ensuring zero downtime, no data loss, systematic cut-over, and a factory approach. We are happy to help in your migration planning process. Please reach out to us for an initial free consultation on migration planning with our solution architects. 

Thanks
OpsHub Team

[Godwin Pearl]

Thank you, @OpsHub for the detailed information. That's helpful. Have a good day!

[OpsHub]

Most Welcome @Godwin Pearl 

[Sudhir_Appfire_]

Hi @Godwin Pearl ,

We are from Bobswift and we have raised a Support request https://bobswift.atlassian.net/servicedesk/customer/portal/1/SUPPORT-10214 on your behalf.

Please login to the Support ticket https://bobswift.atlassian.net/servicedesk/customer/portal/1/SUPPORT-10214 as you will receive updates made on it.

Regards,
Sudhir

[Godwin Pearl]

Thanks @Sudhir_Appfire_  I'm not able to access the url. Thoughts?

[Kinnera]

Hi @Godwin Pearl 

You can sign up to our portal here https://bobswift.atlassian.net/servicedesk/customer/portals/1 and let us know the username so that we can mark you as the reporter so that you will be able to access the ticket.

Thanks
Kinnera

[Godwin Pearl]

@Kinnera  - How do i share the username/email privately?