Import Mantis 1.2.5

[Herbert Mahalek]

Hi,

I'm currently integrating all our old systems into jira. One of our departments had mantis 1.2.5 as there bug tracking tool. Currently jira 5.0 RC2 isn't supporting mantis 1.2.5. The question is, will there be a support for mantis 1.2.5 in the next weeks.

Greetings Herbert

[Herbert Mahalek · Accepted solution]

Hi,

I solved the Problem with a workaround.

I exported the Bugs in mantis and imported them via Jira Rest Api.

Thanks for the help,

Cheers,

Herbert

[Wojciech Seliga]

We try to catch up with 3rd party issue trackers as much as we can afford to.

We are going to add support for newest Mantis version soon, but I cannot give you the exact date. Good thing is that JIRA Importers Plugin release cycle is decoupled from JIRA release cycle, which means that even if we won't do it before JIRA 5.0 final is released, we can quickly add a few weeks later.

BTW: have you actually tried importing from Mantis 1.2.5? In our documentation we mention only these versions which we actually tested the import from, but often new version works flawlessly without any changes on the importer side.

If you could tell us what did not work for you, that would greatly help us quickly fix the problem.

[Herbert Mahalek]

Hi,

I found the following StackTrace in the Jira log:

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown table engine 'InnoDB'

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)

at com.mysql.jdbc.Util.getInstance(Util.java:381)

[Wojciech Seliga]

Hey,

This exception suggests that your MySQL installation is incomplete/broken. I've googled for this exception "com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown table engine 'InnoDB'" and a few people have experienced it as well (in other products) and the problem was solved when they fixed their MySQL setup.

However I don't think that even if you fix MySQL issues on your end, JIM will be able to import the issues. However I do expect problems at a different stage and related to schema changes in Mantis 1.2.5.

Cheers,

Wojtek

[Wojciech Seliga]

Update: in JIRA Importers Plugin 4.1 (which is going to be released in a few days) we officially bump up the version of supported Mantis to 1.2.8. See https://studio.atlassian.com/browse/JIM-647 for more details.