Documentation for JIRA 5.0. Documentation for other versions of JIRA is available too.

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.

(info) Our main website highlights some top reasons why people migrate from FogBugz to JIRA. 

Version 4.0 or later of the JIRA Importers Plugin is compatible with Fogbugz versions 7.3.6 to 8.2.27. The JIRA Importers Plugin requires your FogBugz Server database to be MySQL or MS SQL or MS SQL Express.

 

(info) For the very latest version of the JIRA Importers Plugin, please visit plugins.atlassian.com.
(info) These instructions refer to a FogBugz server behind your firewall. To import from a FogBugz On Demand (SaaS) issue tracker site please follow the instructions for here.

The import process consists of:

  1. Running the Import Wizard to configure the import process and save it into a configuration file. (Note that you can edit your configuration file later by by re-running the Import Wizard and providing the name of your existing configuration file.)
  2. Configuring the connection from your JIRA server to the FogBugz database.
  3. Running the import using your saved configuration file. You will typically do this several times (e.g. once or more for tests, once for production).

These steps are described in more detail below.

On this page:

(warning) The information on this page does not apply to JIRA OnDemand.

How to import from a FogBugz Server

  1. Before you begin, please backup your JIRA data.
  2. Log in to JIRA as a user with the 'JIRA Administrators' global permission.
  3. Select 'Administration' > 'System' > 'Import & Export' > 'External System Import' > 'FogBugz for Your Server'.
  4. The 'Import issues from a FogBugz installation' page will be displayed:
    Screenshot 1: the 'Import issues from a FogBugz installation' page
  5. If you don't yet have a configuration file (or if you want to create a new one, or update the one you have), leave the 'Existing Configuration File' field blank and click 'Next' to create a new Configuration File:
    • Project Key Mappings: For each FogBugz project that you wish to import into JIRA, select the JIRA 'Project category' (if applicable) and the JIRA 'Project key'.
      • To import into an existing JIRA project, type a project key (or project name) that already exists in JIRA.
        (warning) There is no warning or error message if you select an existing key (or existing project name with a different key). The importer will import issues to the project specified by the key (or project name).
      • To create a new JIRA project and import into it, type a project key that does not yet exist in JIRA.
        (info) The JIRA 'Project key' will be the prefix for the IDs of all issues in the given project.
    • Custom Fields: If your FogBugz system contains any custom fields, you can either choose the JIRA custom field to which they will be mapped, or choose to have the importer automatically create a new custom field(s) in JIRA.
      (info) Regardless of whether you specify mapping, the importer will automatically create a JIRA custom field for each extra FogBugz field, unless you un-check the 'Create new custom fields' option on the final 'Import Data' screen (see Screenshot 2 below).
    • Field Value Mappings:
      • 'Priority' field — If you don't specify mappings, the importer 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).
      • Usernames — If you don't specify mapping, the importer will automatically map FogBugz usernames to JIRA usernames (lowercase).
        (info) Regardless of whether you specify mapping, JIRA will automatically create usernames for missing users unless you un-check the 'Create new users' option on the final 'Import Data' screen (see Screenshot 2 below).
      • 'Status' field — It is mandatory to map the FogBugz 'Status' field to specific values of the JIRA 'Status' field, as the JIRA 'Status' field is integral to JIRA workflow (to learn more, please see What is Workflow and Configuring Workflow).
      • 'Resolution' field — If you don't specify mapping, the importer will create corresponding Resolutions in JIRA instead of using the existing ones.
    • Link Types: To learn more about JIRA link types, please see Configuring Issue Linking.
  6. Configure the connection details to your FogBugz database as follows:
    • FogBugz URL — the URL of your FogBugz instance.
    • FogBugz Login — the FogBugz user to use during the import.
    • FogBugz Password — the password of the FogBugz user to use during the import.

    • Database URL— the location of the FogBugz database server. Enter this in the following format:

      jdbc:mysql:host[:port]/databasename?parameters
      • host — the server hosting the FogBugz database. You can specify which incoming TCP connections to allow by using the port parameter (defaults to 3306).
      • databasename — the name of the FogBugz database (usually 'bugtracker').
        (info) The database name can usually be found in the registry. Documentation is at http://bugs.movabletype.org/help/topics/setup/WindowsWhatSetupDoes.html (search for Initialize Registry Settings).
    • Database Login — the database user that JIRA will use to access the FogBugz database.
      (warning) Ensure that this account can access your FogBugz database from the machine where JIRA is running.
    • Database Password — the password of the database user that JIRA will use to access the FogBugz database.
    • Driver Name— The fully qualified name of the base class of the JDBC driver to use:
      • "com.mysql.jdbc.Driver" for MySQL.
      • "org.postgresql.Driver" for PostgreSQL.
    • 'Maximum issues and failues' — If you wish, specify a maximum number of failed issues after which the importer will stop. If you want the import to continue regardless of any failures, leave this field blank. If your FogBugz instance has a large number of issues, it's generally a good idea to run first the importer on a limited number of issues (e.g. 100), then manually inspect the imported issues to confirm whether your configuration file was specified correctly. When the results are satisfactory, you can run the import with no limit.
  7. The importer will display updates as the import progresses, then a success message when the import is complete. You can download the import log if you wish.

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:

In FogBugz

In JIRA

Import Notes

Project

Project

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.)

Area

Component

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.

Milestone

Fix Version

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.

Case

Issue

Every FogBugz case becomes a JIRA issue.

Case ID
ixBug

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 Behaviour).

Summary

Summary

 

Comments

Comments

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

Attachments

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.

Category

Issue Type

You can configure mapping of specific Case Categories to specific Issue Types.

Priority

Priority

You can configure mapping of specific FogBugz values to specific JIRA values.

Status

Status

You can configure mapping of specific FogBugz values to specific JIRA values, provided you create your workflows in JIRA before running the importer.

  • The JIRA 'Status' field is integral to JIRA workflow. To learn more, please see What is Workflow.
  • To create a JIRA workflow, please see Configuring Workflow.
  • To create a JIRA workflow scheme (which you can then associate with appropriate projects and Issue Types), please see Activating Workflow.

Resolution

Resolution

You can configure mapping of specific FogBugz values to specific JIRA values.

Duplicates
BugRelations

Links

You can configure mapping of specific FogBugz link types to JIRA link types.

Computer

Computer

The FogBugz Computer field is imported into a JIRA Custom Field called 'Computer'.

Customer Email

Customer Email

The FogBugz Customer Email field is imported into a JIRA Custom Field called 'Customer Email'.

User

User

You can choose to have the importer automatically create JIRA users for any FogBugz users who do not already exist in JIRA.

  • Users who interacted with the FogBugz system will be created as active accounts in JIRA. Other users will be imported into a special group called "fogbugz-import-unused-users" and will be deactivated.
  • Passwords from FogBugz are not imported (as they are hashed in the database). Users from FogBugz will need to get their passwords emailed to them the first time they log into JIRA.
  • Users with no real name stored in FogBugz will get the portion of their email address (login name) before the "@" character as their Full Name 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.
  • If you are using External User Management, the import process will not be able to create JIRA users; instead, the importer will give you a list of any new users that need to be created. You will need to create the users in your external user repository before commencing the import.
  • If you have a user-limited license (e.g. personal license), and the number of required users is larger than the limit, then the import will be stopped. A page will be displayed showing a list of users that can't be created.

Other fields

Custom fields

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.
Please note that the FogBugz Custom Field plugin is not supported.



See our Getting Help page for details.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.