When migrating from ClearQuest to JIRA, there are some several technical pitfalls which one may encounter. In this post I will detail the main issues which I tackled during the migration process.
The general strategy is to use as much of the built-in JIRA fields as possible, since many abilities and plug-ins uses them by default (such as JIRA Agile). It required effort, but it certainly paid off.
Let’s discuss the details, then:
I was writing a script to modify .CSV files (ClearQuest export results), and it was incredibly complex due to having multi-line fields (“embedded newlines” in CSV jargon).
After some struggling, I came across a built-in module (at least in ActivePerl 5.12.3) called Text::CSV_XS which basically does everything I wanted. I was able to cut my script length by about 60% and get better performance and (seemingly) bug-free results.
This module is easy to use and has good documentation.
Lesson learnt: re-inventing the wheel is not always the best course of action…