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

Skip to end of metadata
Go to start of metadata

About importing from FogBugz OnDemand

JIRA ships with the JIRA Importers Plugin pre-installed, so that you can easily import your bugs from FogBugz OnDemand. Version 3.1 or later of the JIRA Importers Plugin is required. If you have an earlier version you can upgrade it via the Universal Plugin Manager.
(info) These instructions refer to FogBugz OnDemand (Hosted). To import from a FogBugz Server behind your firewall please follow the instructions for here.

On this page:

The import process converts FogBugz OnDemand data as follows:

FogBugz OnDemand

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

External issue ID and External issue URL

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 'External issue 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

 

They are not imported due to limitations of FogBugz Remote API

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.

How to import from FogBugz OnDemand

  1. Before you begin, please back up your JIRA data. (If you have none then you can skip this step.)
  2. Log in to JIRA as as a user with the 'JIRA Administrators' global permission.
  3. Select 'Administration' > 'System' > 'Import & Export' > 'External System Import' > 'FogBugz OnDemand'.
  4. Enter your FogBugz URL, login and password and then click the 'Next' button. The 'Project Key Mappings' step is displayed:
    Screenshot 1: 'Project Key Mappings'
    • The check box of each FogBugz OnDemand project to be imported is selected. To prevent a project from being imported, clear its check box.
    • By default, a new JIRA project for each FogBugz OnDemand project you import will be created. (JIRA automatically suggests a name and key for each of these JIRA projects.)
    • If applicable, select 'Project category' for these JIRA projects.
    • To import a FogBugz OnDemand project into an existing JIRA project, type in the exact name and key of the existing JIRA project.
  5. The Field Value Mappings page with then be displayed with the following options:
    • External fields: This will allow you to transform values of various fields during the import process.
    • Workflow Scheme: Select the JIRA workflow scheme for all projects to use or accept the default.
      • Then the importer will allow you to map values.
  6. The Issue Link Mappings page will then be displayed. This is where you will select how to map FogBugz's Parent/Subcase links in JIRA.
  7. The 'Import Data' page will then be displayed with the following options:
    • 'Create new users' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create new usernames for FogBugz users who do not already exist in JIRA.
    • 'Create new versions' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create new versions for FogBugz 'backlogs' which do not already exist in JIRA.
    • 'Create new components' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create new components for FogBugz components (areas) which do not already exist in JIRA.
    • 'Create new custom fields' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create custom fields for FogBugz fields which do not have a corresponding field in JIRA.
    • '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.
  8. The importer will display updates as the import progresses, then a success message when the import is complete.
    Screenshot 3: the 'Success' page

Congratulations, you have successfully imported your FogBugz OnDemand projects into JIRA! If you have any questions or encounter any problems, please contact Atlassian support.