Documentation for JIRA 6.3. Not using this? See below:
(JIRA 6.2.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

The JIRA Importers plugin, which is bundled with JIRA, allows you to import data from Mantis by connecting to a live Mantis database.

(info) 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).

  • You can choose to map individual fields and field values during the import process, some of which are mandatory.
  • At the end of the Mantis Import Wizard, you will be given the option of creating a Mantis configuration file, which contains the settings you configured whilst running through the Mantis Import Wizard. This is useful if you need to test your Mantis import on a test JIRA server first before performing the import on a production system.

On this page:

Running the Mantis Import Wizard

  1. Before you begin, please backup your JIRA data.
  2. Log in to JIRA as as a user with the JIRA Administrators global permission.
  3. Choose > System. Select Import & Export > External System Import to open the Import external projects page.
    (tick) Keyboard shortcutg + g + start typing external system import
  4. Select the Import button associated with the Mantis option to open the Mantis Import Wizard: Setup page.
  5. On the Mantis Import Wizard: Setup page, complete the following fields/options:

    Mantis URLSpecify 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.
    Selecting this check box reveals/hides the Mantis Login and Mantis Password fields, into which you should specify these user credentials.

    Database Type

    Select the type of database that your Mantis installation uses:

    • PostgreSQL
    • Microsoft SQL Server
    • MySQL
    HostnameSpecify the hostname or IP address of the server running your Mantis site's database server.
    PortSpecify the TCP/IP port that the Mantis site's database server is listening on.
    (tick) This field is automatically populated with the default port value based on the Database Type you choose above.
    DatabaseSpecify the name of your Mantis database (into which Mantis saves its data).
    (info) The database name, username and user password can usually be found in the Mantis file 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
    UsernameSpecify the database user that Mantis uses to connect to its database.
    PasswordSpecify the password of the database user (above) that Mantis uses to connect to its database.
    Use an existing configuration fileLeave 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.
    (info)  Note:
      • If you select this option, you will be asked to specify an Existing Configuration File.
      • If you do not select this option, then at the end of the Mantis Import Wizard, JIRA will create a configuration file which you can use for subsequent Mantis imports (for re-use at this step of the Mantis Import Wizard).
    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.
    (info) If you chose MySQL (above), the Mantis Import Wizard will add several additional connection parameters by default.
  6. Click the Next button to proceed to the Set up project mappings step of the Mantis Import Wizard.

  7. On the Set up project mappings page, select which Mantis projects you wish to import into JIRA.
    (info) All Mantis projects are selected by default, so clear the check boxes under Import of the Mantis projects you do not wish to import into JIRA.
    For Mantis projects you wish to import into JIRA, click in Select a project and then do either of the following:
    • Start typing the name (or key) of a project that already exists in JIRA or use the dropdown menu to select an existing JIRA project.
    • Select Create New from the dropdown menu and in the resulting Add A New Project dialog box, type the following:
      1. A new project Name
      2. A new project Key 
        (info) This will be used as the prefix for all issue IDs in your JIRA project.
      3. The Project Lead.
  8. Click the Next button to proceed to the Set up custom fields step of the Mantis Import Wizard.
    (info) This step will almost always appear because at least one Mantis field is not likely match an existing JIRA field.

  9. On the Set up custom fields page, for each External field  in Mantis which the Mantis Import Wizard cannot match to an existing JIRA field, you can choose to either:
    • have the Mantis Import Wizard automatically create new custom fields in JIRA based on the names of Mantis's fields. This is the default option - whereby the names of the JIRA custom fields to be automatically created appear in the JIRA field dropdown lists.
  10. Click the Next button to proceed to the Set up field mappings step of the Mantis Import Wizard.
  11. On the Set up field mappings page, if there External fields in Mantis whose values you wish to modify before they are imported into JIRA, select the Map field value check boxes next to the appropriate fields.
    (info) Please note that it is mandatory to map Mantis's status (i.e. Status) field to specific JIRA Status field values as the JIRA Status field is an integral part of JIRA workflows.
    • 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
      usernameThe Mantis Import Wizard will automatically map Mantis usernames to JIRA usernames (lowercase).
      priorityThe 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).
      severityThe Mantis Import Wizard will not map values for this field.
      resolutionThe 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.
      (info) 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.

  12. Click the Next button to proceed to the Set up value mappings step of the Mantis Import Wizard.
  13. On the Set up value mappings page, specify JIRA field values for each Mantis field value (as detected by the Mantis Import Wizard).
    (info) Any fields whose Map field value check boxes were selected in the previous step of the Mantis Import Wizard will be presented on this page, including the mandatory status Mantis field.
  14. Click the Next button to proceed to the Set up links step of the Mantis Import Wizard.
  15. On the Set up links page, specify the JIRA link type for each Mantis link type (as detected by the Mantis Import Wizard). To learn more about JIRA link types, please see Configuring Issue Linking.
  16. Click the Begin Import button when you are ready to begin importing your Mantis data into JIRA. The importer will display updates as the import progresses, then a success message when the import is complete.
    (info) Note:
    • If you experience problems with the import (or you are curious), click the download a detailed log link to reveal detailed information about the Mantis Import Wizard process.
    • If you need to import data from another Mantis product/project or site with the same (or similar) settings to what you used through this procedure, click the save the configuration link to download a Mantis configuration file, which you can use at the first step of the Mantis Import Wizard.

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

Tips for importing Mantis data into JIRA fields

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

In Mantis

In JIRA

Import Notes

Project
Sub 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 Behavior).

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
(or a custom field)

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
(or a custom field)

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.

  • The JIRA 'Status' field is integral to JIRA workflow. To learn more, please see What is Workflow.
  • To create a JIRA workflow, please see Configuring Workflow.
  • To create a JIRA workflow scheme (which you can then associate with appropriate projects and Issue Types), please see Activating workflow.

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.

  • Users who interacted with the Mantis system will be created as active accounts in JIRA. Other users will be imported into a special group called "mantis-import-unused-users" and will be deactivated.
  • Passwords from Mantis are not imported (as they are hashed in the database). Users from Mantis will need to get their passwords emailed to them the first time they log into JIRA.
  • Users with no real name stored in Mantis will get the portion of their email address (login name) before the "@" character as their Full Name in JIRA.
  • If you are using External User Management the import process will not be able to create JIRA users; instead, the importer will give you a list of any new users that need to be created. You will need to create the users in your external user repository before commencing the import.
  • If you have a user-limited license (e.g. personal license), and the number of required users is larger than the limit, then the import will be stopped. A page will be displayed showing a list of users that can't be created.

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.

 

53 Comments

  1. I can't find step 7. in JIRA 4.4.3!?

  2. Anonymous

    I'm using Jira V4.4.3 and the UI here is different. There're no "Database URL" or "Driver Name" fields, they've been replaced with "Database Type", "Port" and "Database". Please update the documentation to match.

  3. Anonymous

    Is it possible to exclude some fields during the import (JIRA 5.0.1) ?

    Because I've got an old Mantis with a lot of projects and useless fields...

     

    1. There's no easy way to do it. You can always copy the database and remove custom fields from it.

      1. Anonymous

  4. Anonymous

    What's about the comment restrictions? Is it possible to import the restrictions (private, public) from mantis too? How does it work?

    1. This is not possible. Comment restrictions are not imported.

      1. Anonymous

  5. Anonymous

    Is it possible to import the project tickets which is in open status only.  tx for the reply n advance.

    1. Sure, you can do that, just copy your Mantis database, remove all other than open bugs and then import from this database.

       

  6. Anonymous

    We are planning to import Mantis into a JIRA OnDemand account.  It looks like we'll have to set up a local JIRA first and import the Mantis data there first.  Then import the local JIRA into the JIRA OnDemand.  Will this process bring along attachments or do we need to do more steps?

    1. Hi there,

      Yes, you are right. The process of moving data from Mantis – > JIRA local --> JIRA OnDemand brings along attachments. You might find the following pages useful if you haven't seen them:

      • Importing Issues: How to import data from various systems to JIRA OnDemand, including JIRA local.
      • Backing Up Data: How to get the data from JIRA local and import into JIRA OnDemand. 
  7. Anonymous

    Thanks!  We are now looking at migrating the data from Mantis -> JIRA local -> JIRA JSON Export -> JIRA OnDemand because we need to import into an existing instance/project.  The link you provided was helpful to see how to export the data attachments from the JIRA local, but not clear about importing the data attachments from the backup to OnDemand.  On this page: Importing Issues, I see a topic "Import the data".  Would this import overwrite existing data files in OnDemand (it appears so from earlier in the article)?  Or can you guide me to more specific information about importing attachments into an existing instance/project?

    1. Hi! 

      Unfortunately, it's not possible to directly import JIRA data to JIRA OnDemand without overwriting the existing data. You can work around this by doing a few extra steps as outlined in this comment: Re: Importing Issues

  8. At step 4 i am getting this: Unexpected exception: Invalid column name 'true'.

    Any ideas why? database mssql

    1. Either you're using unsupported Mantis version and database schema is different, or you found a bug in JIM.

    2. We haven't tested Mantis importer with MS SQL. Please open a bug request at https://studio.atlassian.com/browse/JIM and provide import log. I'll try to fix it.

      1. where is import log?

  9. You can extract it from atlassian-jira.log (or just send the whole file). If you atlassian-jira.log may contain information that's sensitive you may open support case at https://support.atlassian.com, so your case will be private and visible only for you and Atlassian.

  10. Mantis 1.2.11 is not mentioned specifically, has anyone tried this version for an import?

     

     

  11. We tried this with mantis 1.2.10 and the final step "Issues" keeps hanging on during the import process.

    Is there any solution for this?

     

    PS: Configuration of the import works fine for all steps.

    1. Please check atlassian-jira.log to see what's going on with the importer when it hangs. You can also request support at http://support.atlassian.com or ask for help on http://answers.atlassian.com

      1. Issue https://support.atlassian.com/browse/JSP-142183 is solved. The progress bar hangs about 25 minutes until it moves forward. Customers should know that.

        1. I can't access the mentioned ISSUE - https://support.atlassian.com/browse/JSP-142183. I am also curious whether an when imports will work with Mantis 1.2.11.

          1. I just went ahead with this and gave it a go.

            I had no issues at all. Worked a treat.

  12. Anonymous

    hello, i have a project in Mantis with some Sub Projects which i want to import in JIRA and i know that sub projects will become "versions" as JIRA does not have sub projects option. after successful import JIRA mix all the issues of sub projects in one single project, things i tried:

    • on the import page i selected the main project and the sub projects but JIRA imported all the issues in one single project
    • on the import page i just selected the main project import it in JIRA, create version and then tried to import sub projects one by one but the results are still same. JIRA import the issues in the main project.

    is there a way i can import the sub projects in JIRA as a version. i am using JIRA 4.4.4.

    thanks in advance.

    1. We don't support them currently, please ask on http://answers.atlassian.com, maybe some will have a clue how to do it easily. And you can raise an issue at https://ecosystem.atlassian.com/browse/JIM so we don't forget about it when planning next versions.

  13. Anonymous

    hello! i'm importing mantis database into JIRA but the import failed to import the attachments from mantis!! how can i resolve this? i had the error bellow.. 

    [13:41:14] FAILED: Failed to attach attachments to issue CT-314

    java.lang.RuntimeException: SQL Exception accessing data
    	at com.atlassian.jira.plugins.importer.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:262)
    	at com.atlassian.jira.plugins.importer.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:232)
    	at com.atlassian.jira.plugins.importer.imports.mantis.MantisDataBean.getAttachmentsForIssue(MantisDataBean.java:118)
    	at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:555)
    	at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:184)
    	at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:25)
    	at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:14)
    	at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:359)
    	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    	at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForTenant(DefaultMultiTenantManager.java:61)
    	at com.atlassian.multitenant.juc.MultiTenantExecutors$WrappedRunnable.run(MultiTenantExecutors.java:160)
    	at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:249)
    	at java.lang.Thread.run(Thread.java:662)
    Caused by: java.sql.SQLException: Column 'id' not found.
    	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055)
    	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
    	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926)
    	at com.mysql.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1144)
    	at com.mysql.jdbc.ResultSetImpl.getString(ResultSetImpl.java:5549)
    	at com.atlassian.jira.plugins.importer.imports.mantis.transformer.AttachmentTransformer.copyAttachment(AttachmentTransformer.java:90)
    	at com.atlassian.jira.plugins.importer.imports.mantis.transformer.AttachmentTransformer.transform(AttachmentTransformer.java:60)
    	at com.atlassian.jira.plugins.importer.imports.mantis.transformer.AttachmentTransformer.transform(AttachmentTransformer.java:29)
    	at com.atlassian.jira.plugins.importer.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:249)
    	... 16 more

     

    1. What Mantis version are you importing from? Seems like it's too old or too new and it's not supported by the importer.

  14. Anonymous

    mantis 1.2.0 i'm using JIRA 4.3

    1. Oh, so old version of JIRA Importers Plugin, that's probably a bug. Please try using a newer version. The SQL query that fails for you is following: "SELECT id,filename,file_type,content,date_added,description FROM mantis_bug_file_table where bug_id=" + ixBug.

      Check you mantis_bug_file_table to see why it doesn't have id column.

  15. Anonymous

    i've check it!! it have an Id column!! I am using the building importer plugin. is it possible to install only new compatible version of imporer plugins instead of reinstall a new version of JIRA ? 

    1. Oh. You cannot install the newest version of JIRA Importers Plugin on 4.3, we currently support 5.x to 6.x, the latest version compatible with 4.3 was 2.7.5 which is really old.

  16. Anonymous

    ok!! thanks! i'm now trying to install a new version of JIRA (5.2.4).. i think my problem will be solved! 

  17. Anonymous

    i have this error "Error connecting to the database: JDBC driver class not found: com.mysql.jdbc.Driver" while connecting to the mantis database.. i even specify a jdbc driver!! may i install something else? i'm using JIRA 5.2.4.1 

    1. Yes, that's correct, JIRA used to be distributed with MySQL driver but it's not longer due to Oracle licensing change. Here's a setup guide - Connecting JIRA to MySQL

  18. Anonymous

    Hye.

    Question 1 : I have JIRA on version 4.4.5 with JIRA Importers Plugin on version 3.5.3. Is it possible to migrate issues from Mantis on version 1.0.6, or only versions of Mantis between 1.1.8 and 1.2.8 (as it's indicated on https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-plugin/version/36 --> "Importer works with Mantis from 1.1.8 to 1.2.8") ?

    Question 2 : the operation of JIRA Importers Plugin will copy issues from Mantis to JIRA (at the end of the operation, the issues are present on Mantis and JIRA) or will move issues from Mantis to JIRA (at the end of the operation, the issues are present only on JIRA and deleted from Mantis) ?

    Thanks in advance.

    1. Ad. 1) it will probably not work, but you can get JIRA Importers Plugin source code and modify it to suit your Mantis version. To obtain source code go to http://my.atlassian.com

      Ad. 2) JIRA Importers Plugin never modifies the external database, it always copies the data

    1. Looks like you're using OnDemand instance which doesn't support Mantis importer. To importer data from Mantis to OnDemand you'll need to use a locally installed JIRA (you can use evaluation license for this), then you'd have to export data from this locally installed instance and import it to your OnDemand instance.

      1. This comment is the only place this seems to be documented.

        Can you please update the Marketplace description for JIRA Importers Plugin to reflect that OnDemand does not support Mantis? It does already mention FogBugz and Bugzilla. Cheers.

  19. I am trying to import from mantis 1.2.15 but without luck. The importer cannot find any projects. Does this have something to do with the mantis version or do I have a different issue?

    I am puzzled as to where I am going wrong. I see that the importer officially does not support v1.2.15 of Mantis but was hoping it would still work (It seems to work with v1.2.11 above). Mantis is installed on the same server as Jira, so all access should be fine. It also isn't complaining on Step 1 "Setup". But for obvious reasons I cannot continue with the import and the "Next" button also is disabled.

    I am running the latest version of JIRA (6.1).

    Any suggestions?

     

    1. Hello Andrew,

      It seems that you have encountered a bug  JIM-1042 - Map projects step is displayed incorrectly Resolved . It is fixed in JIM 6.0.26 which will be released shortly. However I do not guarantee that JIM will be working correctly with Mantis v1.2.15, we haven't tested it yet. 

      1. Thanks for the prompt update.

        That explains it. In the meantime I have managed to actually downgrade to v1.2.8 of Mantis including DB schema downgrade (was easy), but still have the same issue. So it is very likely, that the importer will work with v1.2.15 also since the DB schema is practically identical.

        When do you think we can expect 6.0.26?

        We're kind of stuck at the moment ... (tongue)

        1. It should be available on Marketplace in this week.

          1. Anonymous

            Still no luck with the update! Given that the plug-in gets stuck in step two of the importer process, it's practically useless. Is there a way to elevate the urgency to get the fix released?

  20. Any news on when the fix will be available?

    1. Hi Andrew, I just checked with Support and found out that this fix is not out on Marketplace yet (Marketplace still has version 6.0.25). It should be available soon, though I don't have an exact date. I am sorry I don't have more information. I will see if I can get more details from the developer and, if so, I will let you know.

  21. I just did the upgrade of the importer to 6.0.26 and imported from our Mantis DB v1.2.15. Works like a charm. Thanks for everyone's efforts so far.

    One issue remains which is that

    • Categories become components, BUT
    • the link between issues and components (former categories) gets lost (warning).

    In the manual above it says "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." But when going through the import wizard it doesn't give me this option.

    I would be happy to do what is described here: here but I am not given the option to map Mantis categories to a custom field.

    Any ideas?

  22. I'm trying to import to JIRA my Mantis 1.2.14 data.  I follow the above instructions but when I click the Next button I get an HTTP 404 Error.  The browser I am using is Chrome.  I have verified all the information on the form as correct.  URL, and credentials, and the URL I am using for the Mantis Site is reachable from the JIRA Server.

    1. Currently we are only supporting Mantis up to 1.2.8 - we have never tested the importer with a newer Mantis version. We're planning to release new JIM with support for Mantis 1.2.15, but it won't happen until late March/April.

    2. Hello Rodney,

      We've checked the imporer with Mantis 1.2.15 and 1.2.16 and it seems to be working fine with our sample project. However you're not the first person who has reported to us that JIM throws 404 during Mantis import. Unfortunately, we cannot reproduce that on our test environment. 

      If you're still facing this problem please create an issue under JIM project (https://ecosystem.atlassian.net/browse/JIM) and attach your import log or JIRA log file if possible. That would help us investigate this problem, fix it and/or provide a workaround as soon as possible.

  23. Mantis 1.2.15 may not be officially supported but we have already done the import (as stated above) and it worked pretty flawlessly. You can also downgrade the Mantis DB to 1.2.8. It's not that much work, but actually unneccessary as it works with the 1.2.15 DB version, too.

    Use at your own risk, of course.