How to migrate the data from IBM RTC to Jira

[Raj Asthana]

Hello,

Currently I am using IBM EWM 7.0.2 version.

I have following work items Issue, Defect, Story, Task, Feature and etc. and all these have some custom attributes which populate the data through scripts also.

I know to migrate the data from EWM to JIRA using csv format but following questions for the migration as below is possible:

1. Parent/Child related data
2. work item Attachments
3. script based data
4. what type of data can not be migrated?

Kindly help me to understand the approach of RTC to JIRA migration.

Thank you

[Raj Asthana]

Hello Claspil,

Thank you very much for your answer.

Are you migrating to Jira Data Center (self-hosted) or Jira Cloud (software-as-a-service)? ---- Using On Prem environment. I think so Jira data center.

What is the item hierarchy you use in RTC?  ---- Epic - > Feature - > Story. 3 steps hierarchy

We have some attachments, that also need to imported. How could import the attachment from source to target (Jira)?

What do you mean by "script based data"? --- It means we have some fields which are populating the values based on another value, how to set the filed mandatory based on another field? To implement the such kind of functionality, we need to write the Java script so if we need to import such kind of data whereas my knowledge, I would need to write the script in Jira first then could import. Am I right?

Thank you very much for your answer again.

[Trudy Claspill]

Hello @Raj Asthana 

Welcome to the Atlassian community.

Here is a documentation reference on setting up a CSV file for import to Jira. This is not specific to IBM RTC data.

https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

Are you migrating to Jira Data Center (self-hosted) or Jira Cloud (software-as-a-service)?

If there is not already a comparable field in Jira for the custom attributes you have in RTC you will need to create custom fields in Jira to receive that data.

What is the item hierarchy you use in RTC? In Jira there are just three levels by default:

Epic
|-- "standard" issues (i.e. Story, Task, Defect)
    |-- subtasks

You cannot add levels in between those three. If you use Jira Data Center or Jira Cloud Premium then you can add levels above Epic.

To include attachments in a CSV based migration you will have to put the attachments in a location such that each can be referenced by an https link, which you would include in the CSV. That location will have to be accessible to the destination Jira instance.

What do you mean by "script based data"? I have not worked with IBM RTC so I don't know what you mean by that. If you mean that you have fields that are surfacing data dynamically based on real-time scripting, there is nothing in the CSV import process to accommodate that. You would need to investigate option in Jira to create new scripts for those fields. Be advised that may require a third party app

I have never personally worked on an IBM RTC migration to Jira before, so I don't know what data might exist in the source that could not be migrated to Jira.

[Raj Asthana]

Hello Claspil,

Thank you very much for your answer.

Are you migrating to Jira Data Center (self-hosted) or Jira Cloud (software-as-a-service)? ---- Using On Prem environment. I think so Jira data center.

What is the item hierarchy you use in RTC?  ---- Epic - > Feature - > Story. 3 steps hierarchy

We have some attachments, that also need to imported. How could import the attachment from source to target (Jira)?

What do you mean by "script based data"? --- It means we have some fields which are populating the values based on another value, how to set the filed mandatory based on another field? To implement the such kind of functionality, we need to write the Java script so if we need to import such kind of data whereas my knowledge, I would need to write the script in Jira first then could import. Am I right?

Thank you very much for your answer again.

[Trudy Claspill]

We have some attachments, that also need to imported. How could import the attachment from source to target (Jira)?

As I said, to include attachments in a CSV based migration you will have to put the attachments in a location such that each can be referenced by an https link, which you would include in the CSV. That location will have to be accessible to the destination Jira instance.

What do you mean by "script based data"? --- It means we have some fields which are populating the values based on another value, how to set the filed mandatory based on another field?

The implementation depends on when you need the second field to be required. Possible scenarios:

1. When an issue is being created, if Field A has value X then entry in Field B needs to be required

2. When an issue is being edited, if Field A has value X then entry in Field B needs to be required

3. When an issue is being transitioned (status is being changed), if Field A has value X then entry in Field B needs to be required

4. When an issue is being transitioned (status is being changed), the user has the option to also change the value of Field A, and if Field A has value X then entry in Field B needs to be required

In the cases of 3 and 4 the Workflow feature supports adding Validators to Issue Transitions to validate field data before allowing the transition to complete. No scripting is required.

I work more with the Jira Cloud product than the Jira DC environment. For cases 1 and 2 I know that there are third party plugins that can help with conditional behaviour as described above. Without research I'm not sure what native solutions are available.