Hi guys,

I'm the author of the mentioned tool and I also did the import of the JIRAs
for Flink. Let me know if you encounter any issues.
The tool will create 278 (or your current id) JIRA issues, because its
importing the closed ones as well. Github is treating pull requests and
issues the same way, so it will also create JIRAs for pull requests (which
is fine for you as well I guess).
I also asked infra to turn off the jira notifications for the import. I can
recommend asking them on https://apache.hipchat.com/chat for stuff like
that.

You are now the third incubator podling to use the tool ;) .. I think I'm
putting the tool into its own GitHub repository.

On a side note: I tried out Zeppelin yesterday .. Its working really well!
The maven build worked like charm, the tutorial also worked.
I also started looking into the code for integrating it with Flink. I think
I can create a first prototype quite soon.

Best,
Robert




On Sun, Jan 11, 2015 at 1:17 PM, Alex B. <b...@apache.org> wrote:

> Hey guys,
>
> we just got JIRA up and working (thanks to awesome INFRA!) and I think we
> want subj now.
>
> What I'v learned from Flink
> <https://issues.apache.org/jira/browse/INFRA-7871> example so far is that
> INFRA team is not going to do that for us. Assuming that, I can will take
> care of this transition in a next couple of days.
>
> My current plan is to use some existing tools
> <https://github.com/rmetzger/scratch/tree/github2jira> to dump Github
> issues using it's API and then push them to JIRA though it's API.
>
> Tech Details:
> To keep issue numbers same, it's important to start with empty JIRA project
> as we have it how.
>
> All comments from GH issues will be created under its own userid
> "github-import" with orig. author name added to the comment.
>
> As we have only 57 issues (36 open\21 closed) - be prepared for some
> notification emails. In case that's not appropriate I could try bothering
> INFRA with asking to turn notifications off, so let me know if that's
> desired.
>
> Please, let me know what you think.
>

Reply via email to