Bugzilla からのデータのインポート

インポートプロセスでは、次のデータが Bugzilla データベースから JIRA にコピーされます。

How to import from Bugzilla

1. Before you begin, please backup your JIRA data.
2. Bugzilla システムで Bugzilla の 'サニティーチェック' を実行し、データにエラーがないことを確認します。
3. Log in as a user with the 'JIRA Administrators' global permission.
4. Select 'Administration' > 'System' > 'Import & Export' > 'External System Import' > 'Bugzilla'.
5. The 'Import issues from a Bugzilla installation' page will be displayed:
   Screenshot 1: the 'Import issues from a Bugzilla installation' page
   jira_5-0_import_bugzilla_1.PNG
6. 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 'Use an existing configuration file' box un-checked, and click 'Next' to create a new Configuration File:
   • Project Key Mappings: For each Bugzilla 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.
       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.
       The JIRA 'Project key' will be the prefix for the IDs of all issues in the given project.
   • Custom Fields: If your Bugzilla 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.
     Regardless of whether you specify mapping, the importer will automatically create a JIRA custom field for each extra Bugzilla field, unless you un-check the'Create new custom fields' option on the final 'Import Data' screen (see Screenshot 2 below).
   • フィールド値のマッピング：
     • '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 Bugzilla to newly-created "Normal" in JIRA).
     • Usernames — If you don't specify mapping, the importer will automatically map Bugzilla usernames to JIRA usernames (lowercase).
       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 Bugzilla 'bug_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).
     • 「解決状況」フィールド ー マッピングを指定しない場合、インポーターは既存のものは使用せず、対応する解決状況を作成します。
   • Link Types: To learn more about JIRA link types, please see Configuring Issue Linking.
7. Configure the connection details to your Bugzilla database as follows:
   • Bugzilla URL — the URL of your Bugzilla instance.
   • Specify credentials — tick this box to show/hide the Bugzilla Login and Bugzilla Password fields. Note that if your Bugzilla instance requires authentication and you don't specify credentials, Bugzilla "Big File" attachments will not be imported.
   • Bugzilla Login — the Bugzilla user to use during the import.
   • Bugzilla Password — the password of the Bugzilla user to use during the import.

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

     jdbc:mysql:host[:port]/databasename?parameters

     • host — the server hosting the Bugzilla MySQL database. You can specify which incoming TCP connections to allow by using the port parameter (defaults to 3306).
     • databasename — the name of the Bugzilla MySQL database (usually 'bugs').
       The database name, username and user password can usually be found in the 'localconfig' file in Bugzilla's root directory, or in /etc/bugzilla/.
   • Database Login — the database user that JIRA will use to access the Bugzilla database.
     Ensure that this account can access your Bugzilla database from the machine where JIRA is running.
   • Database Password — the password of the database user that JIRA will use to access the Bugzilla 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.
8. The 'Import Data' page will then be displayed wit 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 Bugzilla 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 Bugzilla 'milestones' 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 Bugzilla components 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 Bugzilla 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 Bugzilla 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.
9. インポーターは、インポートの進行に合わせて更新状況を示し、インポートが完了すると、正常完了したことを示すメッセージを表示します。ご希望の場合は、インポート・ログをダウンロードすることができます。

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