JIM Error for Mantis Import

[Joshua Jacques]

When running the importer, all of my issues import for the most part, and at the end I am getting an error that the project did not successfully complete:

Import completed with 1 error:

• Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state

2014-06-11 11:28:06,603 ERROR - Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state java.lang.RuntimeException: java.lang.Exception: Failed to add users to 'Developers' role for the project 'DOLBUC': Errors: {} Error Messages: [The actor: 'Josh' is not active. Therefore, it is not possible to add it to the project role: '10001'

I am coming from Mantis 1.1.8 and using JIM 5.0.4 -- Any ideas?

I copied the database from Mantis to a new test schema, and tried resetting all users passwords to make them appear "active" but that didnt work.

[pborkowski · Accepted solution]

Hi Joshua,

We have this bug fixed in JIM around 6.1.0 version. It occurs when one of the imported users is inactive and is an asignee to one of the imported issues. I have couple of ideas what can you do:

1. We always recommend first to upgrade your JIRA instance (and JIM Plugin) to the newest availiable version - you won't experience this bug in the newest version.
2. If you can manipulate Mantis database - make all of your users active by changing "enabled" column in "mantis_user_table" to true (or 1, depends on your DBMS)
3. Before the import create "Josh" user (and any other inactive user) in JIRA. Importer will not create new user(and edit existing one) if he already exists, just make sure that you have the same usernames in JIRA and Mantis so importer will find those users.

Either of this three solutions should fix your problem. Hope it helps.

Cheers,

Przemek

[Joshua Jacques]

Thanks for the reply Przemyslaw. I decided to stop wasting time and just installed a local Jira instance of version 5.0, re-ran my import from Mantis, and it worked great. I then upgraded my local version of Jira to 5.2.11 which is our current production environment. I then ran an export of that single project. We are going to do an import into production next week after some testing. Thank you for your assistance.

[Mikhail T]

Przemyslaw, you must be referring to JIM-1137, which does, indeed, claim, that the fixed version is 6.1.0

However, I'm using JIRA-6.1.7 here with JIM-plugin updated to the very latest available as of today -- and am still suffering from this very bug when trying to import two projects in the same JSON. The first project gets imported cleanly, but then the import dies (with this error) and the second project is ignored.

As I said, JIM-plugin is at the latest available version here. Updating the entire JIRA, however, is not as easily done -- it is in active use by several hundred people.

I suppose, the easiet work-around for us would be to temporarily flip the "troublesome" users to "Active", do the import, and flip them back. Obviously, I'd rather the vendor's (expensive) software had fewer bugs in it...

Please, advise. Thank you!

[Mikhail T]

I suppose, the easiet work-around for us would be to temporarily flip the "troublesome" users to "Active"

Argh, that is not possible for some of the users, because they originally came from Active Directory. They are now removed from the AD, so JIRA lists them as "Inactive" -- and it is not possible to change that...

[pborkowski]

I believe it can be connected to this bug: https://ecosystem.atlassian.net/browse/JIM-1327

It's fixed in our SNAPSHOT version, please leave a comment under issue if you would like me to upload it.