Importing Data from FogBugz On Demand

The JIRA Importers plugin, which is bundled with JIRA, allows you to import data from FogBugz On Demand, a 'Software as a Service' (SaaS) issue tracker product.

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

Version 3.1 or later of the JIRA Importers Plugin is required.

These instructions refer to FogBugz On Demand. To import from the downloadable and installable FogBugz for Your Server product, please follow the instructions for here.

On this page:

Running the FogBugz On Demand Import Wizard

If your JIRA installation has existing data, then before you begin, back up your existing JIRA data.

Tip: FogBugz On Demand supports hierarchical issues. During the FogBugz On Demand Import Wizard, you are given the option to recreate this issue hierarchy through JIRA issue links. Hence, before commencing the FogBugz On Demand Import Wizard, you may wish to configure an custom issue link to replicate this hierarchy — for example:

Name — 'Hierarchy'
Outward Link Description — 'parent of'
Inward Link Description — 'child of'

To import issues FogBugz On Demand:

Log in to JIRA as as a user with the JIRA Administrators global permission.
Select Administration > System > Import & Export > External System Import > Import button associated with the FogBugz On Demand option to open the Connect with FogBugz page.
Keyboard shortcut: g + g + start typing external system import

On the Connect with FogBugz page, complete the following fields:

FogBugz On Demand URL	Specify the URL of your FogBugz On Demand site. This is the URL you would normally use to access FogBugz On Demand through a web browser. This is usually of the format `http://myfogbugzondemand.fogbugz.com`
FogBugz Username	Specify the user account that JIRA will use to access issues on your FogBugz On Demand site.
FogBugz Password	Specify the password of the user (above).

Click the Next button to proceed to the Setup project mappings step of the FogBugz On Demand Import Wizard.
On the Setup project mappings page, select which FogBugz On Demand projects you wish to import into JIRA.
All FogBugz On Demand projects are selected by default, so clear the check boxes under Import of the FogBugz On Demand projects you do not wish to import into JIRA.
For FogBugz On Demand 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.
Click the Next button to proceed to the Setup field mappings step of the FogBugz On Demand Import Wizard.
On the Setup field mappings page, if there External fields in FogBugz On Demand 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 On Demand's sStatus (i.e. Status) field to specific JIRA Status field values as the JIRA Status field is an integral part of JIRA workflows.
- The FogBugz On Demand field sStatus (Resolution) (i.e. Resolution), which will be mapped to the JIRA Resolution field, may also appear on this page.
- Select the appropriate JIRA Workflow Scheme in that will be used by the FogBugz On Demand issues you will import into your JIRA project.
  If you are importing your FogBugz On Demand issues into an existing JIRA project, ensure that you choose the JIRA workflow scheme used by that existing JIRA project. Otherwise, your import may not complete successfully.
Click the Next button to proceed to the Setup value mappings step of the FogBugz On Demand Import Wizard.
On the Setup value mappings page, specify JIRA field values for each FogBugz On Demand field value (as detected by the FogBugz On Demand Import Wizard).
Any fields whose Map field value check boxes were selected in the previous step of the FogBugz On Demand Import Wizard will be presented on this page, including the mandatory sStatus FogBugz On Demand field.
Click the Next button to proceed to the Setup links step of the FogBugz On Demand Import Wizard.
On the Setup links page, specify how want to map FogBugz On Demand's Parent / Subcase relationships through a JIRA issue links. To learn more about JIRA link types, please see Configuring Issue Linking.
You may wish to choose the 'Hierarchy' custom issue link you created before running the FogBugz On Demand Import Wizard.
Click the Begin Import button when you are ready to begin importing your FogBugz On Demand 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 On Demand Import Wizard process.

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

Tips for importing FogBugz On Demand data into JIRA fields

The import process converts FogBugz On Demand data as follows:

FogBugz On Demand	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.

Child pages

Importing Data from FogBugz On Demand

Running the FogBugz On Demand Import Wizard

Tips for importing FogBugz On Demand data into JIRA fields