On May 21, 2007, at 14:25 , Mark Brouwer wrote:
Jim Hurley wrote:
We are looking for any advice/insights on importing
issue data into an Apache project using JIRA. We (Sun)
have a bunch of bug/rfe information in an internal bug
tracking tool, and we'd like to (most efficiently) get that
imported into the River project.
I've checked around a little bit, for example:
<http://www.atlassian.com/software/jira/docs/latest/>
<http://wiki.apache.org/general/ApacheJira>
and didn't see a way to do it.
Any thoughts appreciated here to save us some manual
work and time.
thanks -Jim
See also http://mail-archives.apache.org/mod_mbox/incubator-river-
dev/200705.mbox/[EMAIL PROTECTED]
Although I'm not in favor of the current components in Bugtraq for
this project as we had discussed in January/February I think for
now the best thing to do is make the migration as easy as possible
and from there come up with other component names.
The XML import as Fabrizio suggested is not the route to go I
believe. Although JIRA uses it as its internal import/export format
it contains references to the various entities it understands which
are very hard to fill in manually. CVS/Excel, Bugzilla, Mantis and
FogBugz are the only supported formats AFAIK for importing external
issues.
In this case, yes, it's better to go with CSV.
Below the link for the CVS import documentation for the version of
Apache JIRA:
http://www.atlassian.com/software/jira/docs/v3.7.2/csv_import.html
--
Fabrizio Giudici, Ph.D. - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
[EMAIL PROTECTED] - mobile: +39 348.150.6941
