Import from Bugzilla to JIRA with component names appear underneath multiple Bugzilla products


we have been testing JIRA for about one month now. We are a software developing house and currently use Bugzilla as an issue tracker. Right now we are facing a problem with the product/component import from Bugzilla to JIRA. This is one of the last issues to resolve before we can present JIRA to our department head.

We have defined many products in Bugzilla (ca. 25) which in reality reflect modules within our software. Each product in turn has a lot of components (between 5 and 20). In some products there are components with a name which is the same as that for a component in another product.

We do not want to import each Bugzilla product to a separate JIRA project because of the amount of administrative work involved and general usability (post import). Instead we want to import all our Bugzilla products to one JIRA project. However, if there are multiple components with the same name the information to which Bugzilla product they belong will be lost.

For example:

(module = Bugzilla product)

  • Module 1
    • Common
    • Editor
    • Graph
    • Report
    • Search
  • Module 2
    • Common
    • Editor
    • Installation
    • Rules
  • Module 3
    • Common
    • Export

As you can see, some of the listed component names appear underneath multiple modules.
For example, "Common" appears in all modules, "Editor" appears in modules 1 and 2.
For clarity's sake: The bugs stored in "Common" within module 1 are different from the bugs stored in "Common" within module 2 and are different from the bugs stored in "Common" within module 3.

If all modules (Bugzilla products) were to be imported to one JIRA project we would lose the original relationship between modules and components.

We know that there is an add-on called "Subcomponents for JIRA" and we would like to work with it, but have so far not been able to find a simple way to convert the Bugzilla product-to-component relationship to the JIRA component-to-subcomponent relationship automatically during the JIRA import process.

Does anybody have any input that might help us address this issue?

1 answer

1 accepted

0 votes
Accepted answer

Hello Marco,

I don't think it can be done automatically right now. Usual JIM approach in such cases is to import each Bugzilla product as separated JIRA Project, but if you would like to have one JIRA project, I've came up with two possible solutions: Import Modules one by one and rename components after each import or slightly change JIM source code.

Manual work scenario:

  1. Import one Module (product) to JIRA Project
  2. Go to JIRA Project and manually rename Components (e.g. to "Module 1 - Common")
  3. Import rest of the Modules one by one and rename the components after each import
  4. After all of the imports you will have one JIRA Project with a lot of different Components created.
  5. Use Bulk Edit to reassign issues from 'ugly' Components to Subcomponents or Custom Fields.

If you would like to change JIM source code the logic of importing Components can be found in:

  • DefaultJiraDataImporter.importComponents()
  • and class: ComponentTransformer

Thanks for your reply.
We will be going for the following solution: rename the components in the Bugzilla database with a SQL-Script prior to import to JIRA.

If the product_id for "Module 1" equals "1", we will use the following command:
update components set name = CONCAT('Module 1 - ',name) where product_id = 1;
We will repeat this command for every Bugzilla product.

This makes it possible for us to import all Bugzilla components with the product name.
The only thing we have to do after the import is to create a relationship between new components and the subcomponents which have been imported from the Bugzilla product components.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,711 views 17 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you