nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Retaining Bugzilla ID when importing

Fabian Meier1

I am importing 60,000 issues from Bugzilla and for the previous test runs the issue key were identical with the external issue id. However, for the latest test run, they are no longer in sync. I know that this is actually not supported, but I would still like to understand what the order of the import query depends on. Since it worked before I am pretty sure that if I understand the underlying design of the importer better, I can get them in sync again.

It would look a lot better than:

|*Key*|*Summary*|

|BUG-57453|[BUG 59301] Out of memory in web resource module|

Accepted answers

Fabian Meier1

I ended up doing a CSV import, because the order the Bugzilla importer uses is not deterministic.

All comments

Pawel Niewiadomski

Each project has it's own issue id counter, if you import multiple times to the same project the last value is reused and increased, so you're not able to go back to 1 unless you delete the project.

Also you need to keep in mind that some issues could had been moved from project to project in Bugzilla (or deleted if you enabled issue deletetion in Bugzilla) so you'll still can end up with holes in the numbering.

If you really want to have issue key in sync, you can edit the source code for JIRA Importers Plugin and force the issue key manually by setting the key field on ExternalIssue in IssueTransformer).

But mind you that's something not supported and you're on your own.

Pawel Niewiadomski

Depends on JIRA Importers Plugin version you use. In older versions issues were not sorted, so the order was database depenedant. But from JIRA Importers Plugin version 4.1.3 issues are sorted by bug_id (in ascending order, so oldest are first one to be imported).

You can obtain JIRA Importers Plugin source code with JIRA Source code which is accessible through my.atlassian.com

Fabian Meier1

I am importing into an empty project and I do not want to force set the issuekey to external issue id but I want to control the sort order of the bugzilla issues. For one test run it was in sync (meaning bug #1 resulted in ABC-1 and so on) but then something changed and for a second run they are all messy again (bug #1 resulted in ABC-36725).

So the acutal question is: What is the criteria that defines the sort order in which the bugzilla issues are imported?

Besides that I am still interested in how to modify the source code of the importer plugin. Where can I obtain it and do I have to recompile it?

Bob Swift

When you say empty project it is not clear that you deleted the project and re-created it. It must be deleted and recreated to start a 1. If you need more control of the import process, then you can use JIRA Command Line Interface and a script to preserve numbers (holes in the original numbers can be handled by create and the delete of JIRA issue) but it will be more work and slower than the import.

Fabian Meier1

Empty project means I made sure that it start counting from BUG-1 by creating a new project.

I saw that JCLI can import the issues from Bugzilla, but the import is already taking almost a complete weekend and I cannot afford that it takes any longer...

Fabian Meier1

That would make sense, but I don't think this is the case:

BUG-1 ended up having External Issue ID 6536

BUG-2 ended up having External Issue ID 6915

BUG-3 ended up having External Issue ID 7100

...

Why would that happen?

Pawel Niewiadomski

The simplest explanation would be that you use the version older than 4.1.3. If you use a newer version I don't have an answer for you. No clue.

Fabian Meier1

This was the latest version (JIRA Importers Plugin Version 5.0.2) but now that you mention it, I think the first import I did was in fact with version 4.4. They probably broke it in version 5.x. This is good news for me - downgrading to 4.4...

Will post the results

Pawel Niewiadomski

Fabian, it's not that strange. You haven't mentioned that you use GreenHopper. So to clarify and shed some light - GreenHopper will automatically upgrade JIRA Importers Plugin to at least 4.4 because GH uses it internally.

That's why you weren't able to downgrade it. You'd have to disable GH before downgrading JIRA Importers Plugin.

Fabian Meier1

Well, even after disabling Greenhopper, the version of the upgraded / downgraded JIM plugin would not match. For example: I upgraded to JIM 5.0.2, but the screen popping up said I am now running 4.3.2. There is something wrong with the bundled and installed plugins.

But that was actually just one of many problems. The Bugzilla importer behaved everything but deterministic. I can provide you some of the strange logs if you want. I ended up preparing a CSV loadfile just hours before the go live and got most of the information ready "just in time". The CSV load work without any flaws.

I am working with data migration since 10 years now and I have created many highly customized JIRA based sytems that go beyond the current limitations of the software. We even develop cutting edge plugins by ourselves, so I would say that I know what I am doing, but the Bugzilla importer, I don't get...

I would love to give you more details and point out the issues I had with the help of some log files and notes I took.

Fabian Meier1

Sorry, but I am overwhelmed with work after that weekend and the likeliness that we will do another import from Bugzilla is practically 0%. So I hope you understand that my motivation to follow up on this is pretty low. I had already filed a support request regarding the slow import performance and I have since referenced this topic.

If they ever decide to fix the Bugzilla Importer, they can find information in this topic as well as contact me for more information.

Thanks for your help even though I had to use the CSV import in the end

Fabian

Pawel Niewiadomski

Sure, totally understand you.

Pawel Niewiadomski

Sure, totally understand you.

Fabian Meier1

I ended up doing a CSV import, because the order the Bugzilla importer uses is not deterministic.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

import

bugzilla