Bugzilla import FAQ

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問



Importing data from Bugzilla is only available in CSV or JSON format as of JIRA 8.4.

質問

In Bugzilla I have separate products (AKA project in jira) for a bug and improvement. Can I import them to the same project and declaring the improvement product in Bugzilla to became improvement in same project in the jira?

When you import a Bugzilla product into JIRA, you have the option to select which JIRA project the data will be imported to, but there is no option to select the issue type. Bugzilla 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 the time of the import. (For more information about JIRA projects, please see Defining a Project.)

The role is:

(info) Bugzilla のすべてのバグは JIRA で 'Bug' タイプの課題になります。ただし例外として、重大度が 'Enhancement' の Bugzilla 課題は 'Improvement' タイプ、優先度 'Major' の JIRA 課題になります。


So, you can either:

  • Import all tickets from the Bugzilla bug project into JIRA
  1. Make sure all issues in the improvement project have been assigned with severity 'Enhancement' - this will automatically import them as an improvement issue type in JIRA.
  2. Import this tickets to the same JIRA project.
  • Alternatively, import the data to two separate JIRA projects and then run a bulk update to move from one project to the targeted destiny project in the appropriate issue type.



In Bugzilla in addition to severity ( that can be mapped to jira priority) there is the priority field. I have a mix in my Bugzilla for bug in severity major and priority P1 for example. I want this mug to be mapped to jira priority Major P1 that I created. how can i do it?

This group of mixed settings can't be mapped automatically. Create a "Severity" custom field in JIRA. Then you can map the bugzilla priority field into the JIRA priority field, and the severity field from Bugzilla to the custom field that you have created on JIRA.


Does Bugzilla keywords are being automatically imported to Jira labels?

It will be imported in case you map the bugzilla keywords to a Jira custom field.


After importing once: if an issue change a status (for example) will it be updated in a second import?

Upon performing a second migration it will copy only the new issues. The issues that were imported before, and changed in Bugzilla, will remain unaltered because JIRA will not reimport if the External issue ID and External issue URL are checked within an existing issue. These IDs are assigned upon importing for the first time. It will show a message that they have been skipped:

  • (warning) "Nº of issues that already exist" of "Nº of issues that you are importing" issues have been skipped because they already exist in destination projects. 

We are aware of limitations whereby existing issues in JIRA cannot be updated upon reimporting. (info) This is an already reaised feature request for JIM and is being tracked at

Note: the JIM ticket describes the scenario for CSV import, but this behavior occurs on all BugTracking system, as mentioned by Roy Krishna in this comment.

Custom Field behaviour during import from Bugzilla 
  1. JIRA Custom Field be reused it doesn't need to have the same name
  2. JIRA Custom Field be reused it *has to* have a compatible Custom Field Type - The dropdown for each field in "Custom Fields" wizard step will only show Custom Fields that matches the Custom Field Type for that field. Bugzilla Importer will *not* reuse the existing Custom Field if it's type is different than the one expected - Please see the expected Custom Fields types in table below
  3. JIRA Custom Field be reused it needs have a Global Context or it's needs to be already configured for destination project.
  4. What if JIRA already has a Custom Field with the same name - will it show in dropdown? Well it's a bit tricky... First of all dropdown will always show one Custom Field with the name exactly the same as in the Bugzilla - that's a JIM proposition for a field which will be created. If already a field with exact same name exists in JIRA and has a matching type than it also should be displayed in the dropdown - it doesn't allow here a duplicate names, so it will only display one field with the same name. Long story short: if JIRA already has a filed with matching type and the same name - the user will not be able to see if his picking a JIM proposition or an existing field, *but* in that case JIM will always reuse the existing field.
 Bugzilla FieldExpected Custom Field Type in JIRA
bug_url com.atlassian.jira.plugin.system.customfieldtypes:url
bug_severitycom.atlassian.jira.plugin.system.customfieldtypes:select 
priority com.atlassian.jira.plugin.system.customfieldtypes:select
status_whiteboardcom.atlassian.jira.plugin.system.customfieldtypes:text
 Bugzilla Custom Field of type '2' com.atlassian.jira.plugin.system.customfieldtypes:select
Bugzilla Custom Field of type '3' com.atlassian.jira.plugin.system.customfieldtypes:multiselect
Bugzilla Custom Field of type '4' com.atlassian.jira.plugin.system.customfieldtypes:textarea
Bugzilla Custom Field of type '5'com.atlassian.jira.plugin.system.customfieldtypes:datetime
Bugzilla Custom Field of type '6'com.atlassian.jira.plugin.system.customfieldtypes:textfield
Every other Bugzilla Custom Field Type com.atlassian.jira.plugin.system.customfieldtypes:textfield





最終更新日: 2019 年 9 月 11 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.