Documentation for JIRA 5.1.x. Documentation for other versions of JIRA is available too.
The JIRA Importers plugin, which is bundled with JIRA, allows you to import data from Bugzilla by connecting to a live Bugzilla database.
Our main website highlights some top reasons why people migrate from Bugzilla to JIRA.
Version 4.1 or later of the JIRA Importers Plugin is compatible with Bugzilla 2.20 to 4.0.2. Users of older Bugzilla versions will need to first upgrade the Bugzilla database tables to a supported version, using Bugzilla's checksetup.pl
script. The JIRA Importers plugin requires your Bugzilla database to be MySQL or PostgreSQL.
The Bugzilla import process consists of simply running the Bugzilla Import Wizard (below).
Please Note:
On this page:
The information on this page does not apply to JIRA OnDemand.
If your JIRA installation has existing data, then before you begin, back up your existing JIRA data.
On the Bugzilla Import Wizard: Setup page, complete the following fields/options:
Bugzilla URL | Specify the URL of your Bugzilla site. This is the URL you would normally use to access Bugzilla through a web browser. |
Specify credentials | Select this check box if you want to import Bugzilla issues into JIRA, which require user credentials on your Bugzilla site to access them. |
Database Type | Select the type of database that your Bugzilla installation uses:
|
Hostname | Specify the hostname or IP address of the server running your Bugzilla site's database server. |
Port | Specify the TCP/IP port that the Bugzilla site's database server is listening on. |
Database | Specify the name of your Bugzilla database (into which Bugzilla saves its data)./etc/bugzilla/ |
Username | Specify the database user that Bugzilla uses to connect to its database./etc/bugzilla/ |
Password | Specify the password of the database user (above) that Bugzilla uses to connect to its database./etc/bugzilla/ |
Use an existing configuration file | Leave this check box cleared if you do not have a configuration file or if you want to create a new configuration file. Configuration files specify a mapping between fields in Bugzilla and those in JIRA.
|
JDBC connection parameters (in expanded Advanced tab) | The Bugzilla Import Wizard will construct a JDBC-based database URL from the Bugzilla database server details you specify above. JIRA uses this URL to connect to and import issues from Bugzilla. If you need to specify any additional connection parameters to your Bugzilla database, specify them here. |
On the Setup field mappings page, if there External fields in Bugzilla whose values you wish to modify before they are imported into JIRA, select the Map field value check boxes next to the appropriate fields.
Please note that it is mandatory to map Bugzilla's bug_status (i.e. Status) field to specific JIRA Status field values as the JIRA Status field is an integral part of JIRA workflows.
Other External fields in Bugzilla which are likely to appear on the Setup field mappings page are:
External field in Bugzilla | Not choosing the 'Map field value' check box |
---|---|
login_name | The Bugzilla Import Wizard will automatically map Bugzilla usernames to JIRA usernames (lowercase). |
priority | The Bugzilla Import Wizard will automatically create missing values in JIRA and will ensure that the issues are migrated with the correct priority (e.g. "Normal" in Bugzilla to newly-created "Normal" in JIRA). |
resolution | The importer will create corresponding Resolutions in JIRA instead of using the existing ones. |
Select the appropriate JIRA Workflow Scheme in that will be used by the Bugzilla issues you will import into your JIRA project.
If you are importing your Bugzilla issues into an existing JIRA project, ensure that you choose the JIRA workflow scheme used by that existing JIRA project.
On the Setup value mappings page, specify JIRA field values for each Bugzilla field value (as detected by the Bugzilla Import Wizard).
Any fields whose Map field value check boxes were selected in the previous step of the Bugzilla Import Wizard will be presented on this page, including the mandatory bug_status Bugzilla field.
On the Setup links page, specify the JIRA link type for each Bugzilla link type (as detected by the Bugzilla Import Wizard). To learn more about JIRA link types, please see Configuring Issue Linking.
Congratulations, you have successfully imported your Bugzilla projects into JIRA! If you have any questions or encounter any problems, please contact Atlassian support.
During the import process, the following data is copied from the Bugzilla database into JIRA:
In Bugzilla | In JIRA | Import Notes | |
---|---|---|---|
Product | Project | Bugzilla data is imported on a per-project basis. You can either specify an existing JIRA project as the target, or the importer will automatically create a project(s) for you at time of import. (For more information about JIRA projects, please see Defining a Project.) | |
External Project | Project Category |
| |
Version | Affects Version | ||
Component | Component | You can choose to have the importer automatically create your Bugzilla component(s) in JIRA, or choose to have bugs imported into no component in JIRA. | |
Milestone | Fix Version | Versions are imported from Bugzilla (if you choose) and are set to the Un-Released and Un-Archived state. | |
Bug | Issue | Every Bugzilla bug becomes a JIRA issue of type 'Bug', with one exception: a Bugzilla issue with severity 'Enhancement' becomes a JIRA issue of type 'Improvement' and priority 'Major'. | |
ID | External issue ID | Each imported issue will be given a new JIRA ID, and the old Bugzilla ID will be saved into a JIRA custom field called 'External issue ID'. This custom field is searchable, so you can search for JIRA issues by their old Bugzilla ID. If you don't need this custom field, delete it or 'hide' it (as described in Specifying Field Behaviour). | |
Summary | Summary |
| |
Description | Description |
| |
Comments | Comments |
| |
Attachments | Attachments | Attachments are extracted from the Bugzilla database and saved to disk. To specify the location on disk, see Configuring File Attachments. | |
Priority | Priority | You can choose to map one of either the Bugzilla Priority field or the Bugzilla Severity field (see above) to the built-in JIRA Priority field, and the other to a custom field. (Alternatively, you can choose to map both the Bugzilla Priority field and the Bugzilla Severity field to JIRA custom fields.) When importing into the JIRA Priority field, you can configure mapping of specific Bugzilla values to specific JIRA values. | |
Severity | Priority | You can choose to map one of either the Bugzilla Priority field (above) or the Bugzilla Severity field to the built-in JIRA Priority field, and the other to a custom field. (Alternatively, you can choose to map both the Bugzilla Priority field and the Bugzilla Severity field to JIRA custom fields.) When importing into the JIRA Priority field, you can configure mapping of specific Bugzilla values to specific JIRA values. | |
Status | Status | You can configure mapping of specific Bugzilla values to specific JIRA values.
| |
Resolution | Resolution | You can configure mapping of specific Bugzilla values to specific JIRA values. | |
Duplicates | Link | You can configure mapping of specific Bugzilla link types to JIRA link types.
| |
Work History | Work Log | Each Bugzilla worklog report will appear in JIRA as a separate worklog entry. | |
Estimated | Original Estimate | ||
Remaining | Remaining Estimate | ||
Logged | Time Spent | ||
Votes | Voters | If a user has voted one or more times for a Bugzilla issue, a JIRA vote is stored for that user. | |
CC List | Watchers |
| |
User | User | You can choose to have the importer automatically create JIRA users for any Bugzilla users who do not already exist in JIRA.
| |
Status Whiteboard | Status Whiteboard | A JIRA custom field called 'Status Whiteboard' will be created. | |
Other fields | Custom fields | If your Bugzilla system contains any custom fields, you can choose to map them to specific JIRA custom field(s). If your custom fields don't yet exist in JIRA, the importer can automatically create them for you. |
|