JIRA import wizard converts all issues as 'bug' in JIRA.
Is there a way to retain the original Bugzilla issue type? We created the equivalent types in JIRA. Issues tagged as 'bug' will not follow the correct workflow.
There is a good explanation of how JIRA deals with Bugzilla imports in the Bugzilla Import FAQ:
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:
Every 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'.
Please take a look at the Bugzilla Import FAQ for more information on how the import process works.
In light of the above information I would also encourage you to create a ticket on JAC and present your use case to the developers. Once you do that post the URL for the Suggestion ticket you created so the Community can vote on the ticket and add impact.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs