On this page:

Using the JIRA Importers Plugin

The JIRA Importers Plugin can import your bugs from Mantis. Version 1.6 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.)

For the very latest version of the JIRA Importers Plugin, please visit plugins.atlassian.com.

About importing from Mantis

The import process consists of:

1. Running the Import Wizard to configure the import process and save it into a configuration file. (Note that you can edit your configuration file later by by re-running the Import Wizard and providing the name of your existing configuration file.)
2. Configuring the connection from your JIRA server to the Mantis database.
3. Running the import using your saved configuration file. You will typically do this several times (e.g. once or more for tests, once for production).

These steps are described in more detail below.

During the import process, the following data is copied from the Mantis database into JIRA:

How to import from Mantis

1. Before you begin, please backup your JIRA data.
2. In JIRA's default permission scheme (associated with newly created projects), ensure that the 'Browse', 'Create' and 'Comment' permissions are granted to the group 'jira-users' (or a group with the 'JIRA Users' global permission).
3. Log in to JIRA as a user with the 'JIRA System Administrators' global permission.
4. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
5. On the panel on the left, under the title 'Import & Export', click 'External System Import - Beta!'. Then select 'Mantis'.
6. The 'Import issues from a Mantis installation' page will be displayed:
   Screenshot 1: the 'Import issues from a Mantis installation' page
   
7. If you don't yet have a configuration file (or if you want to create a new one, or update the one you have), click the 'Import Wizard' text link (not button) at the bottom of the page. This will guide you through creating a Configuration File:
   • Project Key Mappings: For each Mantis project that you wish to import into JIRA, select the JIRA 'Project category' (if applicable) and the JIRA 'Project key'.
     • To import into an existing JIRA project, type a project key (or project name) that already exists in JIRA.
       There is no warning or error message if you select an existing key (or existing project name with a different key). The importer will import issues to the project specified by the key (or project name).
     • To create a new JIRA project and import into it, type a project key that does not yet exist in JIRA.
       The JIRA 'Project key' will be the prefix for the IDs of all issues in the given project.
   • Custom Fields: If your Mantis system contains any custom fields, you can either choose the JIRA custom field to which they will be mapped, or choose to have the importer automatically create a new custom field(s) in JIRA.
     Regardless of whether you specify mapping, the importer will automatically create a JIRA custom field for each extra Mantis field, unless you un-check the 'Create new custom fields' option on the final 'Import Data' screen (see Screenshot 2 below).
   • Field Value Mappings:
     • 'Priority' field — If you don't specify mappings, the importer will automatically create missing values in JIRA and will ensure that the issues are migrated with the correct priority (e.g. "Normal" in Mantis to newly-created "Normal" in JIRA).
     • Usernames — If you don't specify mapping, the importer will automatically map Mantis usernames to JIRA usernames (lowercase).
       Regardless of whether you specify mapping, JIRA will automatically create usernames for missing users unless you un-check the 'Create new users' option on the final 'Import Data' screen (see Screenshot 2 below).
     • 'Status' field — It is mandatory to map the Mantis 'Status' field to specific values of the JIRA 'Status' field, as the JIRA 'Status' field is integral to JIRA workflow (to learn more, please see What is Workflow and Configuring Workflow).
     • 'Resolution' field — If you don't specify mapping, the importer will create corresponding Resolutions in JIRA instead of using the existing ones.
   • Link Types: To learn more about JIRA link types, please see Configuring Issue Linking.
8. Configure the connection details to your Mantis database as follows:
   • Mantis URL — the URL of your Mantis instance.
   • Mantis Login — the Mantis user to use during the import.
   • Mantis Password — the password of the Mantis user to use during the import.
   • Database URL — the location of the Mantis MySQL database server. Enter this in the following format:

     jdbc:mysql:host[:port]/databasename?parameters

     • host — the server hosting the Mantis MySQL database. You can specify which incoming TCP connections to allow by using the port parameter (defaults to 3306).
     • databasename — the name of the Mantis MySQL database (usually 'bugtracker').
       The database name, username and user password can usually be found in the Mantis file 'config_inc.php' (the default username is "root", default password is empty). See also http://www.mantisbt.org/manual/manual.configuration.database.php
   • Database Login — the database user that JIRA will use to access the Mantis database.
     Ensure that this account can access your Mantis database from the machine where JIRA is running.
   • Database Password — the password of the database user that JIRA will use to access the Mantis database.
   • Driver Name — The fully qualified name of the base class of the JDBC driver to use.:
     • "com.mysql.jdbc.Driver" for MySQL.
     • "org.postgresql.Driver" for PostgreSQL.
9. The 'Import Data' page will be displayed:
   Screenshot 2: the 'Import Data' page
   #* 'Create new users' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create new usernames for Mantis users who do not already exist in JIRA.
   • 'Create new versions' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create new versions for Mantis 'milestones' which do not already exist in JIRA.
   • 'Create new components' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create new components for Mantis components (categories) which do not already exist in JIRA.
   • 'Create new custom fields' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create custom fields for Mantis fields which do not have a corresponding field in JIRA.
   • 'Maximum issues and failues' — If you wish, specify a maximum number of failed issues after which the importer will stop. If you want the import to continue regardless of any failures, leave this field blank. If your Mantis instance has a large number of issues, it's generally a good idea to run first the importer on a limited number of issues (e.g. 100), then manually inspect the imported issues to confirm whether your configuration file was specified correctly. When the results are satisfactory, you can run the import with no limit.
10. The importer will display updates as the import progresses, then a success message when the import is complete.

Congratulations, you have successfully imported your Mantis projects into JIRA! If you have any questions or encounter any problems, please contact Atlassian support.