Updated: Check out Top 5 Reasons to GO JIRA!
After a successful JIRA 4.2 release the JIRA team is excited to announce a smaller, yet significant, beta release: The JIRA Importers Plugin
Importing your existing bug tracker into JIRA
As you may know, the current importer feature in JIRA, aka the external system importer, allows
you to import issues from Bugzilla, Mantis and FogBugz, as well as CSV files and custom Jelly scripts. While this is a great feature, it has its limitations. With each new release of Bugzilla, Mantis or FogBugz, we were only able to address JIRA compatibility issues in the subsequent release of JIRA.
Well this is no longer the case as
we have now extracted the importer code into a JIRA plugin. This
means that development of the external system importer can be done very
quickly and the release of new importer updates is no longer dependant on a
Beta Bugzilla importer
The beta release of the JIRA Importers Plugin allows you to import your Bugzilla bugs
into JIRA. The current Bugzilla versions supported range from 2.20 to 3.6.3.
Bugzilla 3.6.3 was released this week which just goes to show how quickly
we can test and update the new importer!
In addition to moving the importer to a plugin, we have also added some great new features:
- Importing Work History.
- Importing Big File attachments.
- Importing disabled user accounts (do not count towards JIRA user limit).
- Improved import monitoring.
- Improved error handling.
- We’ve also addresses all the bugs that were raised.
For this first beta release we have concentrated on the
Bugzilla importer and in the next few releases we’ll be tackling the
remaining importers: Mantis, Fogbugz and CSV. In the meantime, if you wish to import from
these systems you can continue to use the original
importers included in JIRA.
Please feel free to raise any bugs or feature
requests that you have in the JIRA Importer Project.