![]() 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. What if JIRA already has a Custom Field with the same name - will it show in dropdown? Well it's a bit tricky.JIRA Custom Field be reused it needs have a Global Context or it's needs to be already configured for destination project.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 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.JIRA Custom Field be reused it doesn't need to have the same name.Custom Field behaviour during import from Bugzilla 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. This is an already reaised feature request for JIM and is being tracked at We are aware of limitations whereby existing issues in JIRA cannot be updated upon reimporting. "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.It will show a message that they have been skipped: ![]() These IDs are assigned upon importing for the first time. 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. Upon performing a second migration it will copy only the new issues. It will be imported in case you map the bugzilla keywords to a Jira custom field.Īfter importing once: if an issue change a status (for example) will it be updated in a second import? 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.ĭoes Bugzilla keywords are being automatically imported to Jira labels? Create a " Severity" custom field in JIRA. This group of mixed settings can't be mapped automatically. I want this mug to be mapped to jira priority Major P1 that I created. I have a mix in my Bugzilla for bug in severity major and priority P1 for example. In Bugzilla in addition to severity ( that can be mapped to jira priority) there is the priority field. 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.Import this tickets to the same JIRA project.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.Import all tickets from the Bugzilla bug project into JIRA.(For more information about JIRA projects, please see Defining a Project.)Įvery Bugzilla bug becomes a JIRA issue of type 'Bug', with one exception: a Bugzilla issue with severity 'Enhancement' becomes a JIRA issue of type 'Improvement' and priority 'Major'. 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. Bugzilla data is imported on a per-project basis. 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. Can I import them to the same project and declaring the improvement product in Bugzilla to became improvement in same project in the jira? Questions In Bugzilla I have separate products (AKA project in jira) for a bug and improvement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |