It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Migrate change requests from IBM Clear Quest to JIRA.. Edited

Hi All,

I am very new to Jira. Posting my question here to get some help.

We are trying to migrate the content (Defects and Change requests) from IBM Clearquest to Jira. Started doing research with CSV Import. But with this method we are able to migrate defects but unable to do change requests to Jira.

Can anyone pls give me some ideas on the same. Is this possible to migrate Change requests from CQ to Jira using CSV Importor method? 



1 answer

1 accepted

0 votes
Answer accepted

Hello @vkalakuntla

Welcome to Atlassian Community!

Analyzing this documentation, I believe that changes requests in IBM ClearQuest are used to track/manage the entire development procedure to perform a specific change in the application, composed of Defects and feature requests. Is it correct?

Per my understanding of the applicable scenario here, it seems that Change requests would be Project versions in JIRA, where you are able to track the progress of defects and feature requests in that version and finally release it to your environment when all its targets are complete.

If that's the case, I recommend you to take a look at the documentation about versions provided above. Basically, you will need to perform two steps:

1 - Manually/Bulk Create your Change requests as versions in JIRA, possibly using JIRA REST API or the own JIRA interface

2 - Map the values of the created fix versions to the issues in the CSV and import it, as described in this documentation:

Importing data from CSV

Alternatively to the option above, you could map your Change requests as a higher hierarchy issue type called Epic in JIRA. If that also works for you, it would be a simpler achievement:

1 - You would import through CSV the Change requests as any other issues, but adding them with Epic issue type

2 - Then, you would import your low-level issues (defects) linked below the Epics (Change requests), by mapping the Epic name field value (From the existing Epic) in the Epic link column of the CSV file when importing the defects.

Additionally, you can check the useful documentation below about migration from IBM ClearQuest to JIRA for further clarification about other functionalities:

1.9 Data Migration from ClearQuest

Let me know which options above makes more sense for you and if you have any questions about it.

Thanks for your detailed reply.



You are welcome, Vishnu.

Have a nice day! :)

Hi Petter,

I have been trying to import the issues from CQ to Jira Cloud using CSV Import.

able to import all the fields except Issue history and attachments. As per my research we didn't import the issue history using CSV Import option.

Do you have any idea -  how to import the history from CQ to Jira ?

Pls let me know i am very new to this migration and having very hard time to do the same.



Hello @vkalakuntla

Unfortunately, CSV does not import the issue history, as you mentioned. The only way to import the history of the issues would be by import that data through JSON import, as mentioned in the documentation below:

Importing data from JSON to JIRA

Would that be an option to export data in JSON format from IBM ClearQuest?

Thanks for your reply.

The link you have given is not working . Can you pls chek on the same..

No Clear Quest doesn't have an option to export data in JSON.

Hello @vkalakuntla

Sorry for the broken link. This link should be working:

Importing data from JSON in JIRA Cloud

I'm sorry to hear that the Clear Quest system is unable to export data in the JSON format. That being said, I believe the only option would be to create the file manually if you want to keep the issue history details.

To prepare the JSON file, you should use the standard JSON format, and follow the pattern detailed in the link provided above.

Let me know if there is anything else I can help you with.

Omg!! Creating file manually is not easy thing for me as we have 20-30 projects and each project can have 100's of issues and change requests. 

Preparing JSON for that many projects is quite challenging. Clear Quest export the data in XML. Is this gives any help to me?

And Is there any other option using REST API to import Issue History?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Introducing new features for Jira Software Cloud's roadmap

Hi Atlassian community, A few months ago, we offered a sneak peak of the new hierarchy view on the roadmap. Thank you for all the feedback (and excitement) and for helping us shape the direction of...

24,962 views 116 86
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you