text: The FogBugz importer allows you to import your bugs from an existing FogBugz installation.
  Importing from a FogBugz file is a two step process. First, you will need to create a mapping file by running
  the FogBugz import wizard. (The mapping file is a plain text properties file that you can also manually edit.
  It will map your CSV fields to fields in JIRA.) Then, to perform the import, simply enter the connection details
  and the location of your configuration file.
  Note: Before you begin, please backup your JIRA data.
  The wizard allows you to choose projects, custom fields and issue links to import. Once this is completed, you can save the file
  on the server and use it in the import process.
  To run the FogBugz Import Wizard:
  Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the
  Administration box on the dashboard:
  The 'Import issues from a FogBugz installation' page will be displayed:
  The first step is to choose which projects are to be imported. Choose a valid project key for each project you want to import, and leave blank if you
  do not wish to import the project. In JIRA Enterprise Edition, you can also choose a project category that the project should be
  created in. This will only apply if the project key does not exist and a new project is created.
  The second step is to decide which of the optional FogBugz fields you wish to import. Most of the fields in FogBugz are automatically mapped
  to appropriate JIRA fields. You can choose to map the fields ixBug (internal FogBugz issue id), sCustomerEmail
  (e-mail address of the issue if created by e-mail) and sComputer (custom field) to any existing global JIRA custom field.
  Value mappings are how values from your FogBugz importer can be 'transformed' during import. The fields sPriority,
  sFullName, sComputer and sCategory can have their values mapped. The first screen
  allows you to choose which fields you would like to map values.
  On the next screen, all unique values for each field you selected to be mapped have been displayed. You can now map any of these values
  to a new value. Leave the field blank if you wish to import the value as-is. If you want to clear a field, enter the keyword
  <<blank>>.
  For sPriority and sCategory you will get a select list with the available values in JIRA. sFullName
  refers to the usernames that will be created in JIRA. If you don't specify any particular mappings, the user name will be created
  from the first letter of the first name and the last name, all in lowercase.
  FogBugz has two types of links, Duplicates and BugRelations. On this screen, you can map the links to existing
  JIRA link types. Leave as none to not import the links.
  The final step of the Wizard is to save the file on your server. Please ensure you enter a valid path. You can also choose to continue on with the
  import without saving the file.
  You can also see a preview of the mapping file that will be saved.
  Once you have your configuration file, you can now import the FogBugz file into JIRA.
  The 'Settings' page gives you precise control over what will be imported
  on each import run.
  Once the import has begun you'll be able to follow live progress of the import, with the screen refreshing at around every 10 seconds. You can
  change this value by updating the field at the bottom of the page. The importer also give you stats about what objects have been imported and
  time elapsed so you can have an idea as approximately how long the import will take. You can also choose to Abort the import, which will cease
  importing after the current issue is done.
  Copyright © 2008 Atlassian Pty Ltd. All rights reserved. Your privacy is important to us.