Hello,
I need to import data from IBM Clearquest to my Jira (around 4k issues, 1go attachment) and I need to keep existing workflows.
Which methos is the better to do that ?
About Jelly, To change workflow status I need to do it step by step? Is there cons about jelly?
Jira > 4.4
Cheers,
Manuel.
Community moderators have prevented the ability to post new answers.
CSV import will allow you to import the issues with whatever status you want. The workflows themselves need to be manually created.
Personally, and it was a long time ago, I did by exporting to excel, then ran a load of perl stuff to fix things up the way I wanted, then import using the CSV importer. I wrote a groovy script to bring in the attachments. That could be done with jelly, although it would be ten times more painful.
The workflows themselves need to be manually created.
manually -> I need to update status using Jira interface ? There are 4000 issues :/
----
In my view : I think I can parse Excel, generate Jelly scripts to create issues with attachments and then update issue status thanks to another jelly script. I can parse excel & generate jelly script using a Java program.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Manuel: you don't need to manually update status of imported issues.
Just first configure the desired workflow in your JIRA instance (what is important are statuses/steps, you can always tweak transitions and their conditions/screens/post-functions later (without any need to manually update your issues). Then perform CSV import mapping in the wizard your original statuses in ClearQuest to just created statuses in JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With CSV import, I can import customfields, attachments and set a specific workflow status.
We don't have to make workflow transition to be in the workflow status wanted?
So, compare to Jelly or soap, there is no difference, it's just easier?
Thanks a lot for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> We don't have to make workflow transition to be in the workflow status wanted?
Correct, just map the input column to status.
> So, compare to Jelly or soap, there is no difference, it's just easier?
If CSV import does everything you need, and it sounds like it does, then use that! You said it handles attachments - at the time I did all this (4-5 years ago) it did not, hence the need for my groovy scripts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian just released a ClearQuest to JIRA Migration cookbook that guides evaluators through the prototype setup. It includes best practices on Proof-of-Concept planning and execution, data migration, production approval process and points to relevant add-ons and Experts that can help. http://confluence.atlassian.com/display/ATLAS/JIRA+Cookbook+-+Migration+off+IBM+Rational+ClearQuest It doesn't provide instructions how to sync the two but refers to Experts who could help with a customized interface. |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.