Updated Jira Migration Tool Now Available for Jira Server, D

Easy to Use Migration Tool

Our out of the box migration tool for Jira allows you to simply connect to your instance of Jira (either Cloud, Server or DataCenter) and choose which artifacts you want to migrate:

From there you can connect it to your instance of Spira (SpiraTest, SpiraTeam, or SpiraPlan) and decide whether you want to use an existing product template to create a new one 'on the fly':

The final step is to then map the various Jira artifacts to the ones in Spira. After that is done, you can click the button to start the migration:

Once the import is done, all of your Jira project data is seamlessly migrated over to Spira.

Migration Tool Enhancements

In the most recent update to this migration tool we have added the following enhancements

Migration of Jira Requirements Backlog Hierarchy

The previous version of the Jira migration tool would import of all the Jira issues that map to requirement types as a simple flat list in Spira. However Spira has a powerful requirements management system that allows you to create hierarchical product backlogs, so we have enhanced the migration tool to convert Jira issue dependent associations between requirements into the parent....child hierarchy within Spira:

This makes it easy to get started with Spira, taking your Jira backlog and planning the Epics, Features and Stories without any manual work to connect them:

Migration of Jira Associations

For those user stories, features and epics in Jira that are connected to each other with non-depedent relationships, the updated migration tool will import them as Associations within Spira:

This new Association migration functionality will handle requirement-incident associations as well as incident-incident and requirement-requirement associations.

Migration of Jira Labels

With the introduction of Spira 7.13 we completed adding support for meta tags for all artifact types. Consequently the migration tool can now import Jira labels as meta tags for all Spira artifacts:

This is in addition to the existing handling of Jira custom fields.

Handling of Additional Jira Custom Field Types

This latest version of the Jira migration tool supports additional Jira custom field types, including the following standard and third-party field types:

com.atlassian.jira.plugin.system.customfieldtypes:textfield
com.atlassian.jira.plugin.system.customfieldtypes:urlfield
com.atlassian.jira.plugin.system.customfieldtypes:textarea
com.atlassian.jira.plugin.system.customfieldtypes:freetextfield
com.atlassian.jira.plugin.system.customfieldtypes:selectlist
com.atlassian.jira.plugin.system.customfieldtypes:select
com.atlassian.jira.plugin.system.customfieldtypes:cascadingselect
com.atlassian.jira.plugin.system.customfieldtypes:multiselect
com.sourcesense.jira.plugin.cascadingselect:multi-level-cascading-select
com.atlassian.jira.plugin.system.customfieldtypes:datepickerfield
com.atlassian.jira.plugin.system.customfieldtypes:datetimefield
com.atlassian.jira.plugin.system.customfieldtypes:datetime
com.atlassian.jira.plugin.system.customfieldtypes:numberfield
com.atlassian.jira.plugin.system.customfieldtypes:float
com.atlassian.jira.plugin.system.customfieldtypes:userpicker
com.atlassian.jira.plugin.system.customfieldtypes:versionpicker
com.pyxis.greenhopper.jira:gh-sprint