Jira has a GH migration tool built in - and we've used that a number of times recently. It requires some coordination, and isn't perfect, but it works.
--David On Wed, Mar 25, 2015 at 6:44 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > +Andrew and David (who may know how this is being done recently) > > On Tue, Mar 24, 2015 at 6:47 PM, Alex B. <abezzu...@nflabs.com> wrote: >> Updates on Zeppelin GH->ASF JIRA issue tracker migration: >> >> we are ready to do it now! >> >> Current plan is to use Robert's >> https://github.com/rmetzger/scratch/tree/github2jira >> >> The only question so far is the ASF JIRA credentials for a user which will >> be a "Reporter" of all migrated issues. >> We could either use one of the PPMCs or some kind of "system" level user. > > A few years ago I was using hadoopqa user account to transition > a project from GH issues to JIRA. > > Andrew, David, what is considered best practice these days? > >> Another seems to be controversial matter is the notification on issue >> creation (~500 emails will be created). >> I have contacted INFRA on HipChat before, to ask if that's possible to mute >> notification and was told that it's not preferable way and we should keep >> notifications as those emails supposed to be part of the mailing list >> archive under ASF. > > Personally -- I don't really care that much as long as these issues all go > to a dedicated email address that I can easily filter out. > > Thanks, > Roman.
