Bugzilla to JIRA migration: migrate CLOSED only, JIRA bug# in bugzilla title, bugzilla component to JIRA project, bugzilla version?

Rob Davis2

I'm going to migrate our bugzilla database to our JIRA setup.

I would like to run the 2 systems in parallel, while people get used to the new system and then eventually decommission bugzilla completely. To do this I propose:

1) Migrating closed-only bugzilla bugs (we do need to refer back to what we did). I believe the import feature is customisable:

- Forum post "Custom JIRA Import functionality": http://forums.atlassian.com/thread.jspa?messageID=257350177

- Forum post about selective importing migration"cherry picking import frombugzilla": http://forums.atlassian.com/thread.jspa?messageID=257318941

- There are various tools to do tweaking once the import has been done: http://forums.atlassian.com/thread.jspa?messageID=257344300

2) Have 2 way referencing: JIRA record titles begin with the bugzilla number, e.g. [BUG1234]. A URL to the old bugzilla database in the JIRA record text, maybe a custom field as well. In the Bugzilla record, the title will begin with the new JIRA number, e.g. [JIRA1234]. A URL in the bugzilla comment text to link directly to the JIRA.

The first bit is already possible I believe:

- forum post "[JIRA-user] Linking bugIDs with Bugzilla database "- http://forums.atlassian.com/thread.jspa?messageID=257252612&#257252612

The bugzilla update with JIRA bit would probably be a custom hack, unless anyone knows how to do this/done it already.

3) Freeze closed bugzilla bugs to stop people adding anything new to them in bugzilla. They should re-open the JIRA equivalent. This would be a custom hack to bugzilla I would do myself, unless anyone knows how to do this -

See also http://stackoverflow.com/questions/6439380/bugzilla-closed-fixed-bugs-how-to-stop-further-comments-being-added-to-bug-due

4) Be able to migrate a bugzilla *component* within a project, into its own JIRA project. Want to do this for one or two bugzilla components but not all of them. The rest can be a straight map: bugzilla product->jira project, within that, bugzilla component->jira component.

Your thoughts, suggestions on the above, please. Thanks in advance.

Wojciech Seliga

Hi,

I am responsible for JIRA Importers Plugin (JIM) - which is what you will use here I bet.

First of all forum entries you are referring to in 1) and 2) are now mostly irrelevant. Several months ago importers have been extracted from JIRA core into a separate plugin and most of the stuff (practically everything related to Bugzilla) has been rewritten (or at least refactored). So there can be no code these posts refer to.

As a holder of a commercial JIRA license (including Starter) you can download full source code of JIM and modify it at will for your internal purposes. Because it's a regular plugin it's now even easier than it used to be.

Now coming back to the point: Bugzilla importer is now far more configurable than it used to be. So a lot of things which used to require source code modifications in the past can now be achieved directly from importer UI.

So my proposal (there are probably other as good ways to accomplish the same):

1) import evertying from Bugzilla and then bulk delete all unclosed issues in JIRA. Then, one day, re-import all issues again - the newest JIM (to be available with JIRA 4.4) has the ability to do incremental import (i.e. import only those issues which were not imported previously). If you cannot wait, then you can delete all closed Bugzilla issues in Bugzilla (on some backed-up copy I bet) and do full import again.

2) JIM automatically adds to every importes issue URL (clickable and working) to the original Bugzilla issue. It does not allow you to modify the summary of each issue on the fly though. You would need to modify JIM on your own

3) I am not a Bugzilla expert, but I believe you can change permissions in Bugzilla (editbug) so that people can only view bugs there. To protect bugs from being commented you would probably need to hack Perl - http://www.bugzilla.org/docs/3.6/en/html/cust-change-permissions.html

4) that's simple. Once you import evertying to JIRA (your components will be imported to - usually as JIRA components, unless you decide otherwise) you can search for all issues where component = X and then bulk move them (maximum 1000 at time) to a new project.

I hope it helps.

Cheers,

Wojtek