I'd keep the watchers. If you then add the Watched Issues Gadget ( http://confluence.atlassian.com/display/JIRA044/Adding+the+Watched+Issues+Gadget ), people will have an easier time voting again on their issues.
On Wed, Jan 18, 2012 at 9:30 AM, Alex Harui <aha...@adobe.com> wrote: > Update: In an attempt to simplify the migration of issues from Adobe JIRA > to Apache JIRA, I am seriously considering not migrating votes and > watchers. > > In addition, as I previously proposed, all bugs will be created by some > fictitious user like AdobeFlexSDK (and resolved and/or closed by the same > person as well). I will attempt to cram all previous history into a single > comment field including prior number of votes, original reporter, SDK bug > id, etc. > > We should be able to migrate the list of components and public versions > (and > steps to reproduce). All bugs will be unassigned. > > Yes, that means that folks will have to vote and watch their favorite bugs > again. I realize that is a pain, but it will sort of give us a more recent > poll of what the project members want. > > Anyway, let me know if you think we need to preserve votes and watchers. > > -Alex > > On 1/13/12 1:10 PM, "Nicholas Kwiatkowski" <nicho...@spoon.as> wrote: > > > Alex, > > > > I think that going forward as you stated would be ok. At this point I > > think it's most important to know what the bugs are (and get issue > numbers > > assigned so we can manage them), then to worry about the neuances of some > > of the history from the old repository. > > > > I do think the version numbers and steps to reproduce are extremely > > important however. If the steps-to-reproduce end up as a comment, I > think > > that is acceptable (I just don't want to loose the content), but the > > version number is something very important to filter on, esp. if we will > > eventually be working with multiple versions in our trunk. > > > > -Nick > > > > > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
