The Goldfish Chronicles

There were a couple of comments on my JIRA migration summary. One was that there is a CSV import. I’ve only used this the once, and from the bug reports on its page it does seem to cover comments in some way or other. I’m not sure how you get the CSV though - JIRA’s issue navigator page has an Excel option but that seems to return a HTML (read Office ‘XML’) version. Not something I want to be trying to parse and munge back into CSV. Also, the Excel option does not include the comments.

The other suggestion was to use SOAP. Personally I’m far more a fan of an XMLRPC style API than a SOAP style API, so I tend to avoid SOAP APIs. Mostly when in Java - SOAP in Python was very nice when doing the Commons Bugzilla->JIRA migration. It would have taken more time than the quick RSS restyling to Jelly I was doing, and I doubt it would have helped much beyond being able to create fuller versions with release dates and descriptions.

It would be useful for one of the flaws of the mig4jira script. Currently it doesn’t handle multiple components, affects versions or fix versions. I very rarely ever set multiples, so was pretty confident my data didn’t need me to deal with those. Originally I would have considered Jelly the better choice as it’s a lowest common denominator and makes for a more decoupled process; however Jelly is now deactivated by default in JIRA and you have to modify catalina.sh and restart to turn it on.

This entry was posted on Monday, June 25th, 2007 at 9:49 am and is filed under What I did.... You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.