The tool currently pulls one Adobe issue and creates a new issue in the destination instance, then goes on to the next. I could slow it down if we have to.
On 3/13/12 4:12 PM, "Dave Fisher" <dave2w...@comcast.net> wrote: > > On Mar 13, 2012, at 1:18 PM, Alex Harui wrote: > >> >> >> >> On 3/13/12 1:13 PM, "Carol Frampton" <cfram...@adobe.com> wrote: >> >>> I know Alex considered this option several weeks ago. I believe he was >>> told by Apache infrastructure not to do this but he can correct me if I am >>> wrong. >>> >> I already have this tool written. That's how I was able to convert from the >> Adobe version of JIRA to the Apache version. However, I had to run it >> against an empty JIRA instance and deliver a database dump. Infra currently >> won't let me run it against the actual Apache JIRA instance. > > Can you run your tool so that each JIRA issue is moved one at a time? (Dull, > boring and slow) If so, then that might remove Infrastructures objection which > I believe is more about making "massive" changes that in one way or another > are irreversible and effect other concurrent users. > > Regards, > Dave > > >> >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
