JIRA 4.3 : Migrating from Other Issue Trackers
This page last changed on Feb 10, 2011 by rosie@atlassian.com.
When migrating from other issue trackers, you may wish to take your data with you. Depending on what issue tracker you are migrating from, you are recommended to use one of the methods listed below to import data into JIRA:
1. Built-in importersJIRA ships with the JIRA Importers Plugin pre-installed, so that you can easily import your bugs from Bugzilla, FogBugz or Mantis.
2. CSV ImporterIf you are migrating from a system for which JIRA does not provide a built-in importer, you may be able to import your data into JIRA via CSV format instead. Your system must be able to export your data into a CSV (comma-separated value) file. You can then import the CSV file into JIRA using JIRA's CSV importer: There is also a workaround for importing comments. 3. Third-party scriptsA number of third-party scripts are available on the Internet that support the importing of data into JIRA. These may be a better option for importing data than using the CSV importer.
4. Jelly scriptAnother approach is to write a Jelly script that will import your data. JIRA ships with some Jelly tags that make operations like creating issues in JIRA easy. 5. RPC servicesJIRA ships with an RPC plugin which enables limited remote access to JIRA. It is available through SOAP and XML-RPC interfaces. We recommend using the SOAP interface when possible as it is more complete and will be our primary focus in the future. The JIRA RPC Services page provides a starting point for all your remote procedure call needs. The full source of the plugin is available and you are free to modify and the extend the source. We'd also be happy to accept code contributions to the project, as Simon Mittag has done in the past. Check out the RPC Endpoint Plugin Module for more information. 6. Your own methodIt is possible to use whatever tools you feel comfortable with, to import the data directly into JIRA's database. JIRA's database schema is described in XML format in the WEB-INF/classes/entitydefs/entitymodel.xml file under the JIRA web application. When using this approach please take care to maintain database integrity. See also:
|
![]() |
Document generated by Confluence on Mar 27, 2011 18:34 |