JIRA Importer Plugin Suppoerted Mantis Documentation Update

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Low
    • None
    • Affects Version/s: 7.6.0
    • Component/s: Documentation - All
    • 7.06
    • 4
    • Severity 3 - Minor
    • 0

      Problem Definition:

      Looking at the version of Mantis that is supported for plugin seems to be really old and this is specifically MySQL

      If we go through the documentation for Mantis itself, the mentions 1.2.x it supports for MySQL 5.0.x differ with JIRA which is already 5.6.

      This appears to affect the plugin that uses default_storage_engine that is available for MySQL recent release while 5.0.x is still using storage_engine. The import will fail as JIM will use default_storage_engine when trying to connect to Mantis database.

      jdbc:mysql://<MySQL URL>/mantis\_db?useUnicode=true&characterEncoding=UTF8&sessionVariables=default_storage_engine=InnoDB&autoReconnect=true&useUnicode=true&zeroDateTimeBehavior=convertToNull&useCursorFetch=true&defaultFetchSize=100
      

      Suggested Solution:

      To update the supported Mantis version accordingly.

      Notes:

      • This is detected when using JIRA 7.6 that has JIRA Importer Plugin 8.0.1
      • The same issue not happening using JIRA 7.0 that uses JIRA Importer Plugin 7.0
      • The "mysql-connector-java-5.1.46 driver" could be used as a workaround as some customer reported that it works. But, it does not always work.

            Assignee:
            Daria Shatsylo (Inactive)
            Reporter:
            Julian (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: