Not sure what you mean by "properly". Because of the way JIRA databases work, it is a ton of work to migrate JIRA systems. You need to have the same user names in the destination system and/or map to new names which is impractical especially given that I believe a lot of the Adobe JIRA users are simply gone from the world of Flex. So, the best I think we can do is what we've done, except that we didn't get attachments and may have messed up some of the statuses, duplicated some issues and probably missed a few as well.
On 6/8/13 7:56 PM, "Mark Kessler" <kesslerconsult...@gmail.com> wrote: >Well not sure what to do with them really. Wouldn't mind just knocking >some of them out from time to time. But if you can't replicate them >properly it would be nice at least downgrade them. > >-Mark > > >On Sat, Jun 8, 2013 at 11:13 AM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> On 6/8/13 7:07 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: >> >> >Hi, >> > >> >> You probably don't have much time to write the tools atm either, >>you've >> >> been busy. Should we change the old Adobe imported ones so they >>don't >> >>show >> >> up as major / unassigned issues? >> >-1 Until we know that they are still not bugs that effects the current >> >SDK I'd leave them open. >> If your goal is just to downgrade them from major to minor but leave >>them >> open, I guess I'm ok with that, but it would be better if you could >>check >> the vote count before you do that. I would argue if they had more than >> two or more votes they could still be considered "major". The number of >> votes did not import from Adobe but should be in the comments as a text >> string. >> >> >> -Alex >> >>
