1) the versions would be irrelevant anyway. I'm happy for old issues to have no version, and create the upcoming version in each project to use properly from now on
2) we rarely use this. Let's just change it on a needs basis - Brett Jason van Zyl wrote: > Hi, > > There are a few issues with the movement of the issues. So I'll list > them and then we need to decide what to do: > > 1) I selected the retain option which I assumed would create the > versions in new projects, but the affects/fix version information > appears to have been lost. > > 2) I thought I selected the option I thought would map > Bug/Improvement/etc into their equivalents in the new projects but it > appears that all the types went in as Bugs. > > These are the bigs ones. > > So versions need to be recreated and the workflow needs to be set as > Vincent made a special workflow for us. These I can automate. > > I think if we identify the leads then each of the plugin projects can > be cleaned up quickly and if users take a peek at issues they raised > it probably won't take long. But we can always restore a backup too. I > would prefer not to do that. I think we can clean up the issues in the > plug-in projects relatively quickly. > > Any thoughts? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
