On Thu, Oct 23, 2003 at 10:08:35PM -0400, Noel J. Bergman wrote: > > 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. :-)
FYI, Brett found another smaller bug [1], which we've fixed. > > 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=3966&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. Correct.. extracting just one project and merging into another db is quite a hairy job. We need to preserve inter-issue links, handle conflicts (eg. usernames - I assume project keys are unique), merge permission/notification schemes, deal with custom fields, custom issue types, new/conflicting issue priorities, etc. But that is the general case. For Maven, it can be done by hand, by: 1) getting a data dump 2) deleting irrelevant projects 3) manually incrementing ids to a range where there will be no conflicts 4) importing via SQL into the database, manually resolving conflicts (most likely usernames). I'll volunteer to do this. I'd have to do it anyway to migrate Forrest from issues.cocoondev.org. Looks like a good excuse to play with XQuery :) If we want to go this route, could I get an acct on nagoya, a mysql username and a copy of the database to play with? Then I can start with a JIRA instance in my home dir and the forrest data. Thanks, --Jeff > > --- Noel > [1] http://jira.atlassian.com/secure/ViewIssue.jspa?key=JRA-2474 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
