Documentation for JIRA 4.2. Documentation for other versions of JIRA is available too.

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:

Whichever method you use, you will need to reindex JIRA after you have imported.

If you have a user limited license (e.g. personal license), any users you import over and above your user limit will be created in JIRA without permission to log in to JIRA. You will not be able to select which of your users are assigned login permissions under the user limit, when you perform the import. However, you can change this after the users are imported, by editing user permissions.

1. Built-in importers

JIRA ships with built-in importers for Bugzilla, Mantis and FogBugz. You are recommended to use the relevant built-in importer, if you are migrating from one of these issue tracking systems. See:

2. CSV Importer

If you are migrating from a system which JIRA does not provide a built-in importer for, 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 scripts

A 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.
Third-party scripts are currently available for the following import processes:

Please note, third-party scripts are not supported by Atlassian.
The Atlassian forums may provide helpful information on the third-party scripts that you wish to use.

4. Jelly script

Another 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 services

JIRA 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 method

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.

参考資料



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.