This feature is not supported in FogBugz On Demand.
Importing From Bugzilla
We offer a script for importing bugs from Bugzilla into FogBugz for your Server. The file is called importBugzilla.asp on Windows systems and importBugzilla.php on Unix and Mac systems. It is included with version 4.0 and later. If you have version 4.0 or later, you can access it like this:
FogBugz for Windows: http://SERVERNAME/fogbugz/importBugzilla.asp
FogBugz for Unix: http://SERVERNAME/fogbugz/importBugzilla.php
FogBugz for Mac: http://SERVERNAME/fogbugz/importBugzilla.php
If you don't have version 4.0 or later, you can status.asp">upgrade or click here to download the zipped script file. Unzip this and put it in your FogBugz/website folder; it uses other files in that folder, so you must have version 3.1.9 or later in order to have the files it references. Then bring it up in your browser with a URL like the one above.
The script adds new cases to your existing FogBugz database, and does not currently attempt to convert Bugzilla ID#s to FogBugz bug numbers, nor does it check for duplicates. For the Project, FixFor, and Area in each case, the importer searches the FogBugz tables for existing projects/fixfors/areas with the name given, and if it can't find one it creates a new one. Similarly, the importer will create disabled FogBugz users for any email address it can't find a matching CPerson for; otherwise it will use the existing ixPerson. These created users do not use a FogBugz license, because they are not enabled in FogBugz.
Errors? If you get the error "Server.CreateObject failed: invalid class string", you may have a different version of the MS XML parser than the version used by this script. Currently this script uses Msxml2.XMLHTTP.4.0. If you have XP SP2 you may not have 4.0, you may have 5.0 instead. Run regedit and look in HKEY_CLASSES_ROOT for Msxml2.XMLHTTP.4.0. If there is no 4.0, but there is a 5.0, just change 4.0 to 5.0 in the script here:
Server.CreateObject("MSXML2.xmlHTTP.4.0")
and here:
Server.CreateObject("MSXML2.DOMDocument.4.0")
Importing From Other Tools
For those of you looking to import from something other than Bugzilla: The wide variety of database formats in use for the wide variety of bug trackers in existence makes it hard to devise an import feature that could handle all of them. So, to import your data, you would need to use a database tool. The FogBugz database is pretty straightforward with mostly self-explanatory names, and figuring out a one-to-one mapping of the fields from your existing database to ours should not be very hard. We do offer a 90 day no questions asked money back guarantee, so you could try it and if it just isn't working out request a refund.
If you choose SQL Server for your FogBugz database, DTS (Data Transformation Services) provides a very intuitive interface for doing this. MS Access has import tools as well. If you're using MySQL, you can
click here to find a conversion utility.
One thing to be aware of when manually importing your bugs is that FogBugz does a join across many tables before displaying bugs. So if your bugs are not showing up after importing, make sure that you have filled out all of the foreign keys in the Bug table (you can
consult the FogBugz schema here). In particular, ones that often come up are ixArea or ixFixFor; make sure that there are rows in the Area and FixFor tables and that your bugs are linking to them properly.
Importing from Excel
A user has posted a method of importing from an Excel spreadsheet here.
Importing from Jira
Jira is another common tool which customers wish to import into FogBugz. See this post for information.
