Search the JIRA 5.0.x Beta and RCs Documentation:

Index
Downloads (PDF, HTML & XML formats)
Other versions

This documentation relates to JIRA 5.0.x Beta and RCs only.
The latest official version is JIRA 4.4.x
If you are using JIRA 4.4.x either view this page in the JIRA 4.4.x documentation or visit the JIRA 4.4.x documentation home page.
Skip to end of metadata
Go to start of metadata

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 importers

JIRA ships with the JIRA Importers Plugin pre-installed, so that you can easily import your bugs from Bugzilla, FogBugz, Mantis, Pivotal Tracker, or Trac.

  • Bugzilla Version 2.0 or later of the JIRA Importers Plugin is compatible with Bugzilla 2.20 to 3.6.4. Users of older Bugzilla versions will need to first upgrade the Bugzilla database tables to a supported version, using Bugzilla's checksetup.pl script. The JIRA Importers Plugin requires your Bugzilla database to be MySQL or PostgreSQL.
  • FogBugz Server (behind your firewall) Version 2.0 or later of the JIRA Importers Plugin is compatible with Fogbugz versions 7.3.6 to 8.2.27. The JIRA Importers Plugin requires your FogBugz database to be MySQL or MS SQL or MS SQL Express.
  • FogBugz OnDemand (Hosted) Version 3.1 or later of the JIRA Importers Plugin is required.
  • Mantis Version 2.0 or later of the JIRA Importers Plugin is compatible with Mantis versions 1.1.8 to 1.2.4. The JIRA Importers Plugin requires your Mantis database to be MySQL or PostgreSQL. (The JIRA Importers Plugin has also been reported to work with MS SQL, Oracle and DB2, but it has not been tested against these databases.)
  • Pivotal Tracker Version 2.5 or later of the JIRA Importers Plugin is required.
  • Trac Version 2.6.1 or later of the JIRA Importers Plugin is compatible with Trac version 0.12.2.

On this page:

(warning) The information on this page does not apply to JIRA OnDemand.

2. CSV Importer

If 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. Requests for Non-Supported Importers

We are also tracking requests to add other systems to our built-in importers. We encourage users to vote and comment on the systems they are interested in:

4. Other Non-Supported Methods

There are also a few other non-supported options to get your data into JIRA:
  1. Write a Jelly script that will import your data. JIRA ships with some Jelly tags that make operations like creating issues in JIRA easy.
  2. Create your own scripts to move issues into JIRA,some examples are: Importing data from Trac into JIRA; Migrating Trac to JIRA; and yet another Trac 2 JIRA import.

  3. JIRA ships with an RPC plugin which enables limited remote access to JIRA. It is available through REST, SOAP and XML-RPC interfaces. We recommend using the REST interface when possible as it 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.

  4. It 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.
  5. Finally as a last resort our built-in importer can be extended to support other systems, there is a very limited starting guide for those interested in taking this avenue.

Other references

 

10 Comments

Hide/Show Comments

  1. Oct 23, 2009

    Bob Swift

    Another tool is the JIRA Command Line Interface. With a little SQL and scripting this can either do one time loads or continuous imports from other systems.

    1. Jan 26, 2012

      Bob Swift

      Specifically, see How to import data from external systems or databases

  2. Oct 29, 2009

    Michael Vorburger

    FYI: At http://kenai.com/projects/issuezilla-to-jira/pages/Home we have a tool & instructions how to migrate from an IssueZilla / java.net project tracker.

  3. Nov 04, 2010

    Anonymous

    As a co-op I spent months writing a migration script in SQL from Devtrack to Jira. Had I known how many issues I'd run into, I probably would have just done it by hand. On the other hand, I really learned how to write a SQL script.

  4. Aug 20, 2011

    Anonymous

    has anyone done an integration with test track pro?

    1. Aug 22, 2011

      Anonymous

      You might like to contact ClearVision, based in the UK. They do all kinds of integrations and if they do not have it, they certainly have the skills to create something. I found them on the Atlassian partners page.

  5. Aug 22, 2011

    Anonymous

    ClearQuest users - Appreciate the new Jira importer makes importing easier however the new product Affinity from Clearvision makes moving from ClearQuest to Jira a whole lot easier and you waste allot less time as the product is tuned specifically for this migration. You might also like to know this product will soon allow ClearQuest and Jira users to synchronise tickets across any geographical distance.

  6. Oct 05, 2011

    Anonymous

    An HP Quality Center importer would be HIGHLY useful.  I see many requests for it, but other than third-party sync tools and the CSV approach there's no seamless way to migrate from QC.

  7. Dec 29, 2011

    Simon Tower [Atlassian]

    At the moment, the JIRA Importers Plugin does not retain the worklog history of an issue (E.G. when certain transitions or assignments took place). If you would like this feature included, please visit studio.atlassian.com and check out the JIRA Importers Plugin project to create/vote on feature requests.

  8. Feb 07, 2012

    Anonymous

    I want to integrate Jira with Easit Case Management system. Easit Case Management system will provide xml files and i wish to import this xml file into Jira. Also after successful import when i update issues in Jira, the same should be reflected back in Easit Case Management system and Vice versa.

     

    Please suggest how this can be implemented in Jira