Continuing to dig into this (and the Jira source :) ).
The version problem should be fixable now - small test worked, and will do a full test tomorrow. Found another problem batch-move wise in that it'll lose all of the assign-to's unless those people are on the project already (or if we make it so anyone may be assigned to). Given that 99+% of our issues are assigned to 'commons developer mailing list', which won't make much sense in Jira, I'm going to accept this loss and make it so every issue is unassigned. Hen On 5/5/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
Cancel that. While the migration looks like it'll go fine in testing - we've unearthed a known bug in batch-moving in which affects-version and fix-version can't be retained even when the two projects have the same version. http://jira.atlassian.com/browse/JRA-8248 Jeff (resident Jira expert) is working on a script to fix them post-move and I'll email when things look good to go. Hen On 5/5/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > At some point tonight, I'm going to go ahead and get stuck into > migrating the Jakarta Commons issues from Bugzilla to Jira. I'm on the > US West Coast, so that means in about 6 hours time. > > I'm not going to make the Bugzilla read-only beforehand, instead I'll > leave things open so people can continue to post bits there, then I > can re-run the bugzilla importer in incremental mode if there are any > changes. Otherwise it involves too much time-synching with other > people etc and time in which people can't post new issues. > > I'll keep the list in touch as to how things are going etc. > > Hen >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
