How do I get Jira to map Bugzilla's Version field to the Fix Version/s field?

Daniel McRae_6ozzqv

In Bugzilla, we have used the Version field to identify the version in which the issue was added/fixed. We defined a custom field named "Found In" to identify the version in which a bug was discovered. We have never used the Milestone field.

When I import from Bugzilla to Jira, "Version" is being mapped to "Affects Version/s", "Found In" is mapped to its own custom field, and "Fix Version/s" is left completely empty.

How can I get Jira to map the following:

(Bugzilla -> JIRA)

Version -> Fix Version/s

Found In -> Affects Version/s

Andy Heinzer

At the present time, Jira's importer for Bugzilla won't allow you to map a custom field from Bugzilla into a system field like this in Jira.   There have been other users that have requested this in the past in https://community.atlassian.com/t5/Questions/Bugzilla-import-mapping-custom-field-to-Fix-Version-s/qaq-p/200745

The link in that thread is old though, and the current feature request for this is actually over in https://jira.atlassian.com/browse/JRASERVER-64650

There are some suggestions in that thread to first map the custom field (such as "Found in" in your case) to a new custom field in Jira and then use the Bulk Change feature in Jira in order to update the version field as needed.   If you only have a few versions, this might be a viable solution.  But if you have dozens or hundreds of version numbers in bugzilla, this would be really tedious to try to do via the bulk change.

Alternatively, instead of using the Bugzilla importer template, you might be able to get around this in a different way.  For example using the CSV importer option will allow you to map field names like this.  The problem I can see from here is to figure out how to properly get a csv file of your bugzilla data, and then map each of those fields to the corresponding Jira fields during import.