JIRA

Install

Admin

Use

	JIRA Administrator's Guide Introduction Getting Help Look and Feel Logo, Colours and Timezone Configuring the default Language Configuring the default Issue Navigator Configuring the default Dashboard Overview of Dashboard Portlets Enabling Portlets and Other Plugins Editing the Announcement Banner Enabling Logout Confirmation Email Email Overview Creating a Notification Scheme Customising Email Content Creating Issues & Comments from Email SMTP configuration User Management Managing Users Managing Groups Managing Project Roles Migrating from Groups to Project Roles Enabling public signup and CAPTCHA Integrating JIRA with LDAP Integrating JIRA with Crowd Configuring Trusted Applications Security Overview Global permissions Project permissions Issue security Project Management Defining a Project Assigning members to Project Roles Defining Project Components Defining Project Versions Creating Release Notes for a Version Configuring Project Keys Configuring Fields and Screens Overview Defining 'Resolution' field values Defining 'Priority' field values Defining 'Status' field values Defining 'Issue Type' field values Associating Issue Types with Projects Translating Resolution/Priority/Status/Type Configuring field behaviour Configuring rich-text renderers Associating behaviour with Issue Types Placing fields on screens Associating screens with Issue Operations Associating screens with Issue Types Creating & configuring Custom Fields Custom Field Overview Adding Custom Fields Configuring Custom Fields Configuring Workflow Workflow Activating Workflow Events Importing from Other Systems Importing from Bugzilla Importing from Mantis Importing from FogBugz Overview Step 1. Running the Impor.. Step 2. Importing the Fog.. Importing from Excel/CSV Moving or Archiving Individual Projects Overview Archiving a project Merging JIRA instances Splitting JIRA instances Integrating with Source Control Integrating with CVS and ViewCVS Integrating with Subversion Integrating with Perforce Integrating with ClearCase Integrating with FishEye Configuration Options & Settings Global Settings Enabling Issue Linking Enabling Sub-tasks Enabling Trackback linking Enabling Time Tracking Enabling File Attachments Enabling Thumbnails for Attachments Server Administration Indexing & Search Backing up Data Automated Backups Restoring Data Database Integrity Checker Increasing memory Performance Tips Database Indexing Precompile JSP pages Logging and Profiling Thread Dump Downgrading (Ent to Pro) Downgrading (Ent to Std) Downgrading (Pro to Std) Using robots.txt with Search Engines Appendix A - Extending JIRA Extension Overview Listeners Services Jelly tags JIRA Toolkit Customising Text Developer Guides JIRA Plugins JIRA RPC Overview Creating a SOAP Client Creating an XML-RPC Client Creating Custom Field Types Custom Workflow Elements Creating new Portlets Creating new Reports More.. JIRA Source Building JIRA from source API Documentation

Importing Data From FogBugz

PDF

Overview

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.

Running the FogBugz Import Wizard
Importing your FogBugz file

Note: Before you begin, please backup your JIRA data.

Notes about the FogBugz Importer

Attachments: JIRA will import all attachments stored in the FogBugz dB. 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.
Link rewriting: 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".

Step 1. Running the Import Configuration Wizard

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:

Log in as a user with the 'JIRA System Administrators' global permission.
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:
On the panel on the left, under the title 'Import & Export', click 'External System Import.'
The 'Import Data' page will be displayed. Select 'FogBugz'.
The 'Import issues from a FogBugz installation' page will be displayed:
Click the link 'Run the FogBugz Import Wizard.

Project Configuration

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.

Issue Field Mappings

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

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.

Note

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.

Issue Links

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.

Saving the configuration file

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.

Step 2. Importing the FogBugz file

Once you have your configuration file, you can now import the FogBugz file into JIRA.

Log in as a user with the 'JIRA System Administrators' global permission.
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:
On the panel on the left, under the title 'Import & Export', click 'External System Import.'
The 'Import Data' page will be displayed. Select 'FogBugz'.
The 'Import issues from a FogBugz installation' page will be displayed:
Type the location of your FogBugz file and your configuration file, and click the 'Import' button.

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.