The JIRA Importers plugin, which is bundled with JIRA, allows you to import data from FogBugz for Your Server by connecting to a live FogBugz for Your Server database.
Our main website highlights some top reasons why people migrate from FogBugz to JIRA.Version 4.2 or later of the JIRA Importers plugin is compatible with Fogbugz for Your Server versions 7.3.6 to 8.7.60. The JIRA Importers plugin requires that your FogBugz for Your Server database is MySQL, Microsoft SQL Server or Microsoft SQL Server Express.
The FogBugz for Your Server import process consists of simply running the FogBugz Import Wizard (below):
- You can choose to map individual fields and field values during the import process, some of which are mandatory.
- At the end of the FogBugz Import Wizard, you will be given the option of creating a FogBugz configuration file, which contains the settings you configured whilst running through the FogBugz Import Wizard. This is useful if you need to test your FogBugz import on a test JIRA server first before performing the import on a production system.
These instructions refer to a FogBugz for Your Server, which is an installable implementation of FogBugz that operates behind your firewall. To import from a FogBugz On Demand (SaaS) issue tracker site, please follow the instructions for here.
Running the FogBugz for Your Server Import Wizard
- Before you begin, please backup your JIRA data.
- Log in to JIRA as a user with the JIRA Administrators global permission.
- Choose > System. Select Import & Export > External System Import to open the Import external projects page.
Keyboard shortcut: g + g + start typing external system import
- Select the Import button associated with the FogBugz for Your Server option to open the FogBugz Import Wizard: Setup page.
On the FogBugz Setup page, complete the following fields/options:
Select the type of database that your FogBugz for Your Server installation uses:
- Microsoft SQL Server
Hostname Specify the hostname or IP address of the server running your FogBugz site's database server. Port Specify the TCP/IP port that the FogBugz site's database server is listening on.
This field is automatically populated with the default port value based on the Database Type you choose above.
Database Specify the name of your FogBugz database (into which FogBugz for Your Server saves its data).
If you need to specify an instance ID for your database, do so using the syntax
fogbugzis the name of your FogBugz database and
sqlexpressis your FogBugz database's instance ID. The database name can usually be found in the Windows registry. See http://bugs.movabletype.org/help/topics/setup/WindowsWhatSetupDoes.html and then search for 'Initialize Registry Settings' (for details on how to access the relevant registry keys and values).
Username Specify the database user that FogBugz uses to connect to its database. Password Specify the password of the database user (above) that FogBugz uses to connect to its database. 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 FogBugz for Your Server and those in JIRA.
- If you select this option, you will be asked to specify an Existing Configuration File.
- If you do not select this option, then at the end of the FogBugz Import Wizard, JIRA will create a configuration file which you can use for subsequent imports (for re-use at this step of the FogBugz Import Wizard).
JDBC connection parameters
(in expanded Advanced tab)
The FogBugz Import Wizard will construct a JDBC-based database URL from the FogBugz database server details you specify above. JIRA uses this URL to connect to and import issues from FogBugz for Your Server. If you need to specify any additional connection parameters to your FogBugz database, specify them here.
If you chose MySQL (above), the FogBugz Import Wizard will add several additional connection parameters by default.
Click the Next button to proceed to the Set up project mappings step of the FogBugz Import Wizard.
On the Set up project mappings page, select which FogBugz projects you wish to import into JIRA.
- All projects are selected by default, so clear the check boxes under Import of the FogBugz projects you do not wish to import into JIRA.
For FogBugz projects you wish to import into JIRA, click in Select a project and then do either of the following:
- Start typing the name (or key) of a project that already exists in JIRA or use the dropdown menu to select an existing JIRA project.
- Select Create New from the dropdown menu and in the resulting Add A New Project dialog box, type the following:
- A new project Name
- A new project Key
This will be used as the prefix for all issue IDs in your JIRA project.
- The Project Lead.
- Click the Next button to proceed to the Set up custom fields step of the FogBugz Import Wizard.
- On the Set up custom fields page, for each External field in FogBugz which the FogBugz Import Wizard cannot match to an existing JIRA field, you can choose to either:
- have the FogBugz Import Wizard automatically create new custom fields in JIRA based on the names of FogBugz's fields. This is the default option - whereby the names of the JIRA custom fields to be automatically created appear in the JIRA field dropdown lists.
- Click the Next button to proceed to the Set up field mappings step of the FogBugz Import Wizard.
- On the Set up field mappings page, if there External fields in FogBugz 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 FogBugz's sStatus (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 FogBugz which are likely to appear on the Set up field mappings page are:
External field in FogBugz Not choosing the 'Map field value' check box sCategory The FogBugz Import Wizard will automatically create missing issue types in JIRA and will ensure that the issues are migrated with the correct issue type. sCustomerEmail The FogBugz Import Wizard will not map values for this field. sComputer The FogBugz Import Wizard will not map values for this field. sFullName The FogBugz Import Wizard will automatically map FogBugz usernames to JIRA usernames (lowercase). sPriority The FogBugz 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 FogBugz to newly-created "Normal" in JIRA). sStatus (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 FogBugz issues you will import into your JIRA project.
If you are importing your FogBugz issues into an existing JIRA project, ensure that you choose the JIRA workflow scheme used by that existing JIRA project.
- Click the Next button to proceed to the Set up value mappings step of the FogBugz Import Wizard.
- On the Set up value mappings page, specify JIRA field values for each FogBugz field value (as detected by the FogBugz Import Wizard).
Any fields whose Map field value check boxes were selected in the previous step of the FogBugz Import Wizard will be presented on this page, including the mandatory sStatus FogBugz field.
- Click the Next button to proceed to the Set up links step of the FogBugz Import Wizard.
- On the Set up links page, specify the JIRA link type for each FogBugz link type (as detected by the FogBugz Import Wizard). To learn more about JIRA link types, please see Configuring Issue Linking.
- Click the Begin Import button when you are ready to begin importing your FogBugz data into JIRA. The importer will display updates as the import progresses, then a success message when the import is complete.
- If you experience problems with the import (or you are curious), click the download a detailed log link to reveal detailed information about the FogBugz Import Wizard process.
- If you need to import data from another FogBugz product/project or site with the same (or similar) settings to what you used through this procedure, click the save the configuration link to download a FogBugz configuration file, which you can use at the first step of the FogBugz Import Wizard.
Congratulations, you have successfully imported your FogBugz projects into JIRA! If you have any questions or encounter any problems, please contact Atlassian support.
Tips for importing FogBugz for Your Server data into JIRA fields
During the import process, the following data is copied from the FogBugz Server database into JIRA:
FogBugz 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.)
You can choose to have the importer automatically create your FogBugz components in JIRA, or choose to have bugs imported into no component in JIRA.
Versions are imported from FogBugz (if you choose). After importing, you can manually set appropriate versions to the Released state in JIRA if you wish.
Every FogBugz case becomes a JIRA issue.
Bug Import ID
Each imported issue ('case') will be given a new JIRA ID, and the old FogBugz ID will be saved into a JIRA custom field called 'Bug Import ID'. This custom field is searchable, so you can search for JIRA issues by their old FogBugz ID. If you don't need this custom field, delete it or 'hide' it (as described in Specifying Field Behavior).
FogBugz allows for links to other issues to be automatically generated by using the format "bug issueId" or "case issue id". After import, any string matching this pattern will be rewritten to their new JIRA key. For example, a comment "Please see case 100" may be rewritten to "Please see IMP-100".
Attachments are extracted from the FogBugz database and saved to disk. Any e-mail issues will be parsed for attachments and the e-mail text saved as a comment. The dates and user attaching the attachments will be retained.To specify the location on disk, see Configuring File Attachments.
You can configure mapping of specific Case Categories to specific Issue Types.
You can configure mapping of specific FogBugz values to specific JIRA values.
You can configure mapping of specific FogBugz values to specific JIRA values, provided you create your workflows in JIRA before running the importer.
You can configure mapping of specific FogBugz values to specific JIRA values.
You can configure mapping of specific FogBugz link types to JIRA link types.
The FogBugz Computer field is imported into a JIRA Custom Field called 'Computer'.
The FogBugz Customer Email field is imported into a JIRA Custom Field called 'Customer Email'.
You can choose to have the importer automatically create JIRA users for any FogBugz users who do not already exist in JIRA.
If your FogBugz 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.