Right, I see your point. Being XML I'm sure concatenating them and modifying the unique IDs isn't going to be a huge issue though - I'm sure at some point in the past someone has had to do this? We possibly need a way to do it consistently as other projects join ASF and bring their previous issue tracking with them too.
I'd say its worth checking out on jira-user first - the friendly guys at Atlassian should be able to help out. Cheers, Brett > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Friday, 24 October 2003 12:09 PM > To: Brett Porter > Cc: [EMAIL PROTECTED]; Serge Knystautas; [EMAIL PROTECTED] > Subject: RE: *** HEADS UP *** JIRA MOVING > > > > bugzilla import is completely broken in 2.4.1, > > whereas it works quite well in the 2.5 beta :) > > Aha! I was wondering about that problem. :-) > > > But regarding maven and codehaus projects moving - I > currently agree > > with Jason that we should wait until Apache's bugzilla has > been moved > > at least, then worry about other projects. Minimise the > risk of things > > falling > apart. > > Unless Jira 2.5 has additional import/export capabilities not > mentioned in their Jira 2.5 notes > (http://forums.atlassian.com/thread.jspa?forumID=46&threadID=3 966&tstart=0), that won't work. The bugzilla import is different from the Jira XML import/export. I can import bugzilla into an existing Jira system, but the Jira import is a REPLACE operation. It is used for backup or migration to another DB server, but not for selective migration. --- Noel
