Importing data from FogBugz On Demand

Migrating from other issue trackers

On this page

Related content

Still need help?

The Atlassian Community is here for you.

Ask the community

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

(info) 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, which is a SaaS implementation of FogBugz.

Running the FogBugz On Demand Import Wizard

Before you begin: If your JIRA installation has existing data — Back up your existing JIRA data. 

(tick) 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 a 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:

  1. Log in to JIRA as as a user with the JIRA Administrators global permission.
  2. Choose > System. Select Import & Export > External System Import to open the Import external projects page.
  3. Select FogBugz On Demand to open the Connect with FogBugz page.

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

    FogBugz On Demand URLSpecify 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.
    (info) This is usually of the format http://myfogbugzondemand.fogbugz.com
    FogBugz UsernameSpecify the user account that JIRA will use to access issues on your FogBugz On Demand site.
    FogBugz PasswordSpecify the password of the user (above).

  5. Click the Next button to proceed to the Setup project mappings step of the FogBugz On Demand Import Wizard.

  6. On the Setup project mappings page, select which FogBugz On Demand projects you wish to import into JIRA.

  7. (info) All FogBugz On Demand projects are selected by default, so clear the checkboxes 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 drop-down menu to select an existing JIRA project.
    • Select Create New from the drop-down menu and in the resulting Add A New Project dialog box, type the following:
      1. A new project Name
      2. A new project Key
        (info) 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 Setup field mappings step of the FogBugz On Demand Import Wizard.
  9. 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 checkboxes next to the appropriate fields.
    (info) 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.
      (warning) 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.
  10. Click the Next button to proceed to the Setup value mappings step of the FogBugz On Demand Import Wizard.

  11. 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).
    (info) Any fields whose Map field value checkboxes 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.

  12. Click the Next button to proceed to the Setup links step of the FogBugz On Demand Import Wizard.
  13. On the Setup links page, specify how want to map FogBugz On Demand's Parent / Subcase relationships through a JIRA issue link. To learn more about JIRA link types, please see Configuring issue linking.
    (tick) You may wish to choose the 'Hierarchy' custom issue link you created before running the FogBugz On Demand Import Wizard.
  14. 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.
    (info) 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. See Defining a project for more information about JIRA projects.

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

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 create a JIRA workflow, please see Working with workflows.
  • To create a JIRA workflow scheme (which you can then associate with appropriate projects and Issue Types), please see Managing your workflows.

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.

Last modified on Mar 23, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Related content

Powered by Confluence and Scroll Viewport.