clearvision - importing with jim and other tools

Clearvision CMAtlassian APE

Migrating to Jira using JIM (and other tools)

http://www.clearvision-cm.com

Agenda

• Who are Clearvision?• Why Migrate to Jira?• The old ways…• The new ways…

• Jira Importer

• An example of migrating from ClearQuest to Jira

• Additional challenges, information and hints• Affinity

• v1.0• v2.0


Who are Clearvision?

• Gerald Tombs, Technical Director• 25 years of software development experience• 15 years of Configuration Management

• Andy Pallett, Software Developer

• Company History• Partnerships with IBM Rational, Atlassian,

Intland, Black Duck• Specialise in Open Source technologies


Why migrate to Jira?


A few reasons…

• Because you have issues! (sorry…)• Mergers and Acquisitions• Licensing costs• Greater efficiency and productivity• Scalability and extensibility• Reduced Administration overhead


The old way

• Long-winded, hard to read scripts• Bugzilla to Jira @ 2,332 lines

• Interacting at a Database level• Dangerous• Could potentially cause huge amounts of

downtime• Future upgrades could be a pain• Slow


Jira Importer


The new way!

• A Jira Plugin• Comes bundled with Jira installations

• Built-in importers• Bugzilla (> v2.0)• FogBugz Server (Behind Firewall or Hosted)• Mantis (> v2.0)• Pivotal Tracker (>v2.5)• Trac (>2.6.1)

• CSV Importer


From ClearQuest to Jira

• An example of using the JIM

• Screenshots and explanations to follow…


ClearQuest to Jira – .csv file


ClearQuest to Jira – Mappings


ClearQuest to Jira – Complete


ClearQuest to Jira – Importing


ClearQuest to Jira – Log OutputINFO - ------------------------------INFO - Importing: IssuesINFO - ------------------------------INFO - Only new items will be importedINFO - Importing issue: ExternalIssue{externalId=autoid-XXX, summary=spelling error in login screen, issueType=null}INFO - Importing issue: ExternalIssue{externalId=autoid-XXX, summary=sales tax incorrect if item deleted, issueType=null}INFO - Importing issue: ExternalIssue{externalId=autoid-XXX, summary=cancel sale doesn't correctly repaint, issueType=null}INFO - Importing issue: ExternalIssue{externalId=autoid-XXX, summary=want more help on inventory report, issueType=null}INFO - Importing issue: ExternalIssue{externalId=autoid-XXX, summary=columns out of alignment, issueType=null}


Additional Information

• When using an exported CSV from ClearQuest, additional tweaks still required• New lines require ‘escape characters’• Multi-value select fields

• Could bulk edit issues, but not always an option

• Currently, links are not supported between issues


Affinity


Affinity

• Developed by Clearvision in 2011

• Currently at version 1.0• Delivered as part of a professional service

• Developed to make a Consultants life easier

• 4 steps to complete migration• Data export• Mapping generation• Data mapping• Data import


Affinity Bridging

• Nearing the end of development

• v2.0 will be released with Jira to Jira functionality• Bi-directional bridging• Server and Jira Plugin

• Jira CQ to be released soon after v2.0


Overview

• Background of Clearvision• Why more companies are migrating to

Jira• Old migration techniques• New, faster and safer migration

techniques• A working example – ClearQuest to Jira

via JIM• Introduction to Affinity v1.0

• And the upcoming Affinity v2.0 (including bridging!)


Thanks for listeningAny questions?

clearvision - importing with jim and other tools

Technology