Documentation for JIRA 5.2. Documentation for other versions of JIRA is available too. 
![]()
The JIRA Importers plugin, which is bundled with JIRA, allows you to import data from Mantis by connecting to a live Mantis database.
Our main website highlights some top reasons why people migrate from Mantis to JIRA.
Version 4.2 or later of the JIRA Importers plugin is compatible with Mantis versions 1.1.8 to 1.2.8. The JIRA Importers plugin requires that your Mantis database is MySQL, PostgreSQL or Microsoft SQL Server. We have also received reports that the JIRA Importers plugin works with Oracle and DB2 databases. However, we have not tested this plugin against these databases.)
The Mantis import process consists of simply running the Mantis Import Wizard (below).
On this page:
On the Mantis Import Wizard: Setup page, complete the following fields/options:
| Mantis URL | Specify the URL of your Mantis site. This is the URL you would normally use to access Mantis through a web browser. |
| Specify credentials | Select this check box if you want to import Mantis issues into JIRA, which require user credentials on your Mantis site to access them. |
| Database Type | Select the type of database that your Mantis installation uses:
|
| Hostname | Specify the hostname or IP address of the server running your Mantis site's database server. |
| Port | Specify the TCP/IP port that the Mantis site's database server is listening on. |
| Database | Specify the name of your Mantis database (into which Mantis saves its data).config_inc.php. (Typically, the default username is "root" and the default password is empty). See also http://www.mantisbt.org/manual/manual.configuration.database.php |
| Username | Specify the database user that Mantis uses to connect to its database. |
| Password | Specify the password of the database user (above) that Mantis uses to connect to its database. |
| Use an existing configuration file | Leave this check box cleared if you do not have a configuration file or if you want to create a new configuration file. Configuration files specify a mapping between fields in Mantis and those in JIRA.
|
| JDBC connection parameters (in expanded Advanced tab) | The Mantis Import Wizard will construct a JDBC-based database URL from the Mantis database server details you specify above. JIRA uses this URL to connect to and import issues from Mantis. If you need to specify any additional connection parameters to your Mantis database, specify them here. |
Click the Next button to proceed to the Set up project mappings step of the Mantis Import Wizard.
Other External fields in Mantis which are likely to appear on the Set up field mappings page are:
External field in Mantis | Not choosing the 'Map field value' check box |
|---|---|
| username | The Mantis Import Wizard will automatically map Mantis usernames to JIRA usernames (lowercase). |
| priority | The Mantis Import Wizard 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). |
| severity | The Mantis Import Wizard will not map values for this field. |
| resolution | The importer will create corresponding Resolutions in JIRA instead of using the existing ones. |
Select the appropriate JIRA Workflow Scheme in that will be used by the Mantis issues you will import into your JIRA project. If you are importing your Mantis issues into an existing JIRA project, ensure that you choose the JIRA workflow scheme used by that existing JIRA project.
Congratulations, you have successfully imported your Mantis projects into JIRA! If you have any questions or encounter any problems, please contact Atlassian support.
During the import process, the following data is copied from the Mantis database into JIRA:
In Mantis | In JIRA | Import Notes | |
|---|---|---|---|
Project | Project | Mantis data is imported on a per-project basis. You can either specify an existing JIRA project as the target, or the importer will automatically create a project(s) for you at time of import. (For more information about JIRA projects, please see Defining a Project.) | |
Category | Component | You can choose to have the importer automatically create your Mantis components in JIRA, or choose to have bugs imported into no component in JIRA. | |
Version | Fix Version | Versions are imported from Mantis (if you choose). After importing, you can manually set appropriate versions to the Released state in JIRA if you wish. | |
Bug | Issue | Every Mantis bug becomes a JIRA issue of type 'Bug'. | |
ID | Bug Import ID | Each imported issue will be given a new JIRA ID, and the old Mantis ID will be saved into a JIRA custom field called 'Bug Import ID'. This custom field is searchable, so you can search for JIRA issues by their old Mantis ID. If you don't need this custom field, delete it or 'hide' it (as described in Specifying Field Behaviour). | |
Summary | Summary |
| |
Description | Description | Within text, Mantis links (e.g. #1234) are converted to JIRA links (e.g. TST-123). | |
Comments | Comments | Within text, Mantis links (e.g. #1234) are converted to JIRA links (e.g. TST-123). | |
Attachments | Attachments | Attachments are extracted from the Mantis database and saved to disk. To specify the location on disk, see Configuring File Attachments. | |
Priority | Priority | You can choose to map one of either the Mantis Priority field or the Mantis Severity field (see below) to the built-in JIRA Priority field, and the other to a custom field. (Alternatively, you can choose to map both the Mantis Priority field and the Mantis Severity field to JIRA custom fields.) When importing into the JIRA Priority field, you can configure mapping of specific Mantis values to specific JIRA values. | |
Severity | Priority | You can choose to map one of either the Mantis Priority field (see above) or the Mantis Severity field to the built-in JIRA Priority field, and the other to a custom field. (Alternatively, you can choose to map both the Mantis Priority field and the Mantis Severity field to JIRA custom fields.) When importing into the JIRA Priority field, you can configure mapping of specific Mantis values to specific JIRA values. | |
Status | Status | You can configure mapping of specific Mantis values to specific JIRA values, provided you create your workflows in JIRA before running the importer.
| |
Resolution | Resolution | You can configure mapping of specific Mantis values to specific JIRA values. | |
Relationships | Links | You can configure mapping of specific Mantis relationship types to JIRA link types.
| |
CC List | Watchers |
| |
User | User | You can choose to have the importer automatically create JIRA users for any Mantis users who do not already exist in JIRA.
| |
Other fields | Custom fields | If your Mantis system contains any custom fields, you can choose to map them to specific JIRA custom field(s). If your custom fields don't yet exist in JIRA, the importer can automatically create them for you. |
|
3 Comments
Anonymous
Jan 17, 2013hello, i have this error message while importing mantis database into JIRA mysql database.. "13-01-17 15:51:15,575 ERROR - Impossible de relier la demande de 8291 � 7779 par un lien nomm� 'Relates'�: Impossible de trouver la cl� de demande import�e pour l'ID" (most of the link import fail). I am using JIRA 5.2.4.1 and mantis 1.2.2.
i also notice that attachments are 0kB.. i don't manage to resolve these problems!!
SusanA
Jan 18, 2013Hello, I am sorry you are having problems. Your best bet would be to contact JIRA Support. Please click the Get Support link at the bottom of this page for further assistance and good luck.
Anonymous
May 03, 2013Users in Groups 'mantis-imported-unused-users' and 'mantis-import-disabled-users' will not be disabled after import.