Rally to Jira migration

Inna S

Hi, 

I saw a number of posts on the subject with no single relevant answer.

Some old ones refer to solutions that do not exist anymore.

One short video found online is a joke.

So, 

beyond the CSV export from Rally, that would give a file per issue type and would contain the references to the related items, what is the best way to import the data into Jira?

We have stories (several levels of), defects, several levels of portfolio items, test cases and test sets and tasks.

We also have releases and iterations. 

Also there are projects and users, some of them have left the company long ago, but we keep the owner's information on the issues because this helps.

The main issue is recreating relations between related items. 

As we have several years of work in the system, the volume is quite large and the manual linking is out of question.

 

Any suggestions?

Thank you.

Nic Brough -Adaptavist-

So there's a couple of things in here that need to be separated out because of the way Jira structures its data.

The main one is that you'll need to consider two types of data - configuration and issue data are separate.

Your issue data is not a problem - it's what the CSV import is for.  One line of CSV per issue, simple.

But most of the configuration data is not importable with CSV (the exception is data in select-list type fields - the CSV import can be told to create new options for select-list fields when it finds it in your CSV.  If, for example, you have a field called "colour" which has options Red, Green and Blue, if the import contains Yellow for an issue, the import can create the Yellow option)

Your issue structure (hierarchy) will need to be created, and you'll need to set up the releases and iterations before you import (although if you do that with "versions", they're a select-list type thing so you can tell the import to create them from the issue data)

But, the good news is that the CSV import can bring in your hierarchy and realtionships.

Jira's base hierarchy is Epic -> Issue -> Sub-task.

If you want to import an Epic / Issue relationship, the best thing to do is import all the Epics first, so that you have issue keys for them, then run a second import for all the Issues.  You add a column for "Epic Link" into that second import, and populate it with the issue keys you have for the Epics.

Sub-tasks are easier, you can do them with their parent issues in one file.  In the csv, you give each issue a unique key of some sort (it gets imported into the "external id" field), and then for each sub-task, you put the unique key of its parent into a parent-id column.

Last you can import "issue links" from CSV as well - see https://confluence.atlassian.com/jirakb/how-to-import-issue-links-from-a-csv-file-in-jira-740262715.html

I think that broadly covers all the different relationships that Jira has, but I don't know if that covers all the different ways Rally might be holding your issue relationships?  Are there others you might need to convert to a Jira relationship?