Importing Data from FogBugz for Your Server

Running the FogBugz for Your Server Import Wizard

1. Before you begin, please backup your JIRA data.
2. Log in to JIRA as a user with the JIRA Administrators global permission.
3. Choose Administration at the top right of your screen. Then choose System > Import & Export from the menu bar and click the External System Import tab to open the 'Import external projects' page.
   Keyboard shortcut: g + g + start typing external system import
4. Select the Import button associated with the FogBugz for Your Server option to open the FogBugz Import Wizard: Setup page.
   

5. On the FogBugz Import Wizard: Setup page, complete the following fields/options:

   Database Type	Select the type of database that your FogBugz for Your Server installation uses: PostgreSQL Microsoft SQL Server MySQL
   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 fogbugz;instance=sqlexpress (where fogbugz is the name of your FogBugz database and sqlexpress is 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. Note: 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.

6. Click the Next button to proceed to the Set up project mappings step of the FogBugz Import Wizard.
   
   
   

7. 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:
     
     1. A new project Name
     2. A new project Key
         This will be used as the prefix for all issue IDs in your JIRA project.
     3. The Project Lead.
8. Click the Next button to proceed to the Set up custom fields step of the FogBugz Import Wizard.
   
9. 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.
   • create your own custom fields in JIRA to map data from FogBugz's fields. To do this, choose Other from the JIRA field dropdown list and specify the name of your custom field in the new field appearing immediately below Other.
10. Click the Next button to proceed to the Set up field mappings step of the FogBugz Import Wizard.
    
11. 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.

12. Click the Next button to proceed to the Set up value mappings step of the FogBugz Import Wizard.
    
13. 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.
14. Click the Next button to proceed to the Set up links step of the FogBugz Import Wizard.
15. 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.
16. 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.
    
    Note:
    
    • 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: