You are not logged in. Click here to log in.

codebeamer Application Lifecycle Management (ALM)

Search In Project

Search inClear

Importing Data from Bugzilla to CodeBeamer

This feature is not maintained and supported anymore

If you wish to import issues, tasks or bugs into a codeBeamer Tracker use importer tools. This document describes the use of two importer tools bundled into


One tool is used for importing data from Mantis and the other, from Bugzilla.

The Bugzilla Importer tool has been developed for importing bug data from existing Bugzilla databases into a CodeBeamer 4.2+ installation.

This tool is a stand-alone Java application which uses the CodeBeamer Web Service API to remotely connect to a CodeBeamer server. You can run the tool using a 1.4 or newer Java Runtime Environment.

Concept Equivalences

Bugzilla has a subset of the features available in CodeBeamer and, as a general rule, all Bugzilla concepts
directly apply to CodeBeamer. However, there are also some naming differences for the concepts. The following are the concept equivalences between Bugzilla and CodeBeamer:

product -> project Bugzilla products are the equivalent of CodeBeamer projects.
bug -> tracker item The importer tool creates CodeBeamer tracker items for each Bugzilla bug and puts them in the project's Bug tracker.
bug_id -> Bugzilla ID Bugzilla bug IDs differ from the CodeBeamer bug IDs. However, the import tool defines a custom field for the Bug tracker named Bugzilla ID (not visible by default) which contains the original bug ID. For each imported bugzilla bug the value of the Bugzilla ID field is set in the tracker item.
component -> category Bugzilla components map to CodeBeamer categories.

Bugzilla Versions Supported

Several Bugzilla versions are supported. Since the tool directly accesses the database, various Bugzilla database variants might impose problems. Currently there is a clear separation between the Bugzilla 2.0 database version and more recent versions. In general, minor database differences are related to the way bug property fields are stored in the bugs table: either in clear text or referenced by a foreign key.

The natural tendency in newer Bugzilla versions is to transform the clear text entries into external entities referenced by a foreign key.

Information on the wide range of Bugzilla database schema versions is available at:

Finding the Importer

The Bugzilla Importer tool has been part of the CodeBeamer installation kit starting with version 4.2. You can find it at the following path:


Running the Importer

For convenience, an executable version of the tool is also bundled. The supplied run.bat file can be used to run it.

The CodeBeamer service connection parameters are specified from the command line in this format:

<program> service-URL login password [version=old] [productName]

Specify the version=old parameter only if your Bugzilla version is older than 2.16.

The optional productName argument is used for importing a single product at a time. If this parameter is missing, all products are imported to the CodeBeamer repository. When importing a Bugzilla product and a CodeBeamer project with that name already exists, the imported data will be merged into the existing project without overwriting the existing data.

The tool connects to the Bugzilla database using the JDBC API. The JDBC connection parameters can be changed by editing one of these files (extracted from the

codebeamer-importers-${CODEBEAMER_VERSION}.zip file):

  • (when using only the run.bat file) the contents of the bin\com\intland\codebeamer\importer\bugzilla\ file,
  • (when running with build.xml) the contents of the src\com\intland\codebeamer\importer\bugzilla\ file. The Apache Ant makefile will automatically copy the updated property file to the bin directory.

By default, the tool supports Bugzilla versions 2.16+. To switch back to older Bugzilla versions, please use the version=old command line parameter.

All imported users have their password set by default to changeme.

Modifying the Importer

The provided source code is suitable for further modification and customization based on individual requirements.

The supplied build.xml Apache Ant makefile provides basic support for command line compilation and running.


The Bugzilla Importer tool provides verbose logging to the console. The bugzilla-importer.log contains a verbatim copy of the console output. The bugzilla-importer.err file contains potential server side or client side errors that the tool might encounter while running.