Mantis import issue type field

[sebastien morpourgo]

Hi,

I am looking at importing data from mantis in Jira.

My probleme is that importing Mantis issues will always result in creating JIRA issue of type BUG, even if the defined workflow for the priously created workflow only contains 4 other issue types.

I have looked at http://confluence.atlassian.com/display/JIRA/Importing+Data+From+Mantis
Nothing is explained about this.

I even had a look at the plugin source file "MantisImportBean.java". I can see that the final issue type in jira imported issue is always BUG : (line 719)

Hi,

I am looking at importing data from mantis in Jira.

My probleme is that importing Mantis issues will always result in creating JIRA issue of type BUG, even if the defined workflow for the priously created workflow only contains 4 other issue types.

I have looked at http://confluence.atlassian.com/display/JIRA/Importing+Data+From+Mantis
Nothing is explained about this.

I even had a look at the plugin source file "MantisImportBean.java". I can see that the final issue type in jira 
imported issue is always  BUG : (line 719)

        // A severity of 10 means this is a feature request, not a bug
        if (resultSet.getInt("severity") == 10) // todo put this in the mappingbean
        {
            issueObject.setIssueTypeId("" + IssueFieldConstants.NEWFEATURE_TYPE_ID);
            issueObject.setPriorityId("" + getMantisFeaturePriority());
        }
        else
        {
            issueObject.setIssueTypeId("" + IssueFieldConstants.BUG_TYPE_ID);
            issueObject.setPriorityId(mappingBean.getPriority(resultSet.getInt("severity")));
        }

Is there any way to map Mantis:[CUSTOM] Issue Category to Jira:Issue Type instead of creating a new custom field with the same name in JIRA.

Indeed, the fields corresponding to each JIRA issue (other than bug issue) are defined specifically to each issue type 
(and thos fields do not exist in the bug issue type. => therefore, I loose all my specific field if the importing type is not kept.

Can you tell me how to create in JIRA (while importing) ussues with the right type ? Corresponding to a MANTIS custom field ?

Thanks for your help.

M. MORPOURGO

Is there any way to map Mantis:[CUSTOM] Issue Category to Jira:Issue Type instead of creating a new custom field with the same name in JIRA.

Indeed, the fields corresponding to each JIRA issue (other than bug issue) are defined specifically to each issue type (and thos fields do not exist in the bug issue type. => therefore, I loose all my specific field if the importing type is not kept.

Can you tell me how to create in JIRA (while importing) ussues with the right type ? Corresponding to a MANTIS custom field ?

Thanks for your help.

M. MORPOURGO

[Wojciech Seliga · Accepted solution]

Hey,

As you can see from the source code only when severity of a Mantis issue is 10 (which AFAIK corresponds to "feature" severity) then JIRA Importers Plugin will map it to New Feature in JIRA. In all other cases Mantis issues will be imported as "Bugs".

If you don't like this behaviour you have 2 options:

• modify JIRA Importers Plugin source code and recompile it (as any other JIRA plugin using Atlassian Plugin SDK).
• import issues as bugs, but populate an additional custom field with issue category data and then perform bulk edit (once all isssues are imported to JIRA) changing in a single batch all issues with given value of this custom field to a requested issue type. In order not to lose any fields on the import, I would suggest configuring initially all fileds as global (not just applicable to a concrete issue type in JIRA), then peforming the import and only when you "clean up" after the import using builk edit (and changing issue types), then changing field configurations (or custom fields context(s)) in JIRA so that these fields are applicable to only selected issue types.

[Eric Trousset]

• modify JIRA Importers Plugin source code and recompile it (as any other JIRA plugin using Atlassian Plugin SDK).

Where/how can we get the source code ?

[SteveM]

I think the source code would be available with the JIRA source code. Paying customers can download the JIRA source code (through my.atlassian.com I believe).

[Eric Trousset]

Where/how can we get the source code ?