You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by James Taylor <ja...@apache.org> on 2014/01/07 00:55:17 UTC
transferring Github issues to JIRA?
Hello,
Anyone out there know of an automated way of transferring over Github
issues to JIRA? We're in the process of transferring over our existing
Phoenix Github-based open source project to our Apache incubator project
and automating the seeding of the initial JIRAs would be very helpful.
Thanks,
James
Re: transferring Github issues to JIRA?
Posted by Jake Farrell <jf...@apache.org>.
Hey James
Thanks for making a ticket for it. Times can vary depending on what comes
up, we are working through the backlog and someone should get to it shortly
-Jake
On Mon, Jan 13, 2014 at 7:39 PM, James Taylor <ja...@apache.org>wrote:
> Thanks, Jake. I filed https://issues.apache.org/jira/browse/INFRA-7179and attached the CSV. Do you know what the turnaround time typically is?
> Please let me know if I can help in any way.
>
> James
>
>
> On Wed, Jan 8, 2014 at 1:45 PM, Jake Farrell <jf...@apache.org> wrote:
>
>> The github plugin is not installed in our jira, I would recommend that you
>> go with the csv route as Steve mentioned
>>
>> -Jake
>>
>>
>> On Wed, Jan 8, 2014 at 4:24 PM, Steve Rowe <sa...@gmail.com> wrote:
>>
>> > Sorry Andy, I don’t know if Infrastructure can/will assist with using
>> that
>> > plugin, but it can’t hurt to ask, and making an INFRA ticket should work
>> > for that.
>> >
>> > I searched INFRA issues for github issue migration and found none that
>> > involved the Atlassian plugin - they all used github CSV export when was
>> > then imported to JIRA by Infrastructure (AFAICT):
>> >
>> > https://issues.apache.org/jira/browse/INFRA-3596
>> > https://issues.apache.org/jira/browse/INFRA-3761
>> > https://issues.apache.org/jira/browse/INFRA-5951
>> >
>> > I see you already have the PHOENIX project set up in JIRA (
>> > https://issues.apache.org/jira/browse/PHOENIX), so that should simplify
>> > the import task whichever way you end up going.
>> >
>> > Good luck,
>> > Steve
>> >
>> > On Jan 7, 2014, at 3:20 PM, Andrew Purtell <ap...@apache.org> wrote:
>> >
>> > > So that means we need an INFRA ticket to plug that in and run an
>> import?
>> > >
>> > >
>> > > On Mon, Jan 6, 2014 at 4:16 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > >
>> > >> Atlassian provides a plugin for that:
>> > >>
>> > >>
>> >
>> https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-github-plugin
>> > >>
>> > >>
>> > >> On Mon, Jan 6, 2014 at 6:55 PM, James Taylor <jamestaylor@apache.org
>> >
>> > >> wrote:
>> > >>
>> > >>> Hello,
>> > >>> Anyone out there know of an automated way of transferring over
>> Github
>> > >>> issues to JIRA? We're in the process of transferring over our
>> existing
>> > >>> Phoenix Github-based open source project to our Apache incubator
>> > project
>> > >>> and automating the seeding of the initial JIRAs would be very
>> helpful.
>> > >>> Thanks,
>> > >>> James
>> > >>>
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > > Best regards,
>> > >
>> > > - Andy
>> > >
>> > > Problems worthy of attack prove their worth by hitting back. - Piet
>> Hein
>> > > (via Tom White)
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>> >
>>
>
>
Re: transferring Github issues to JIRA?
Posted by James Taylor <ja...@apache.org>.
Thanks, Jake. I filed https://issues.apache.org/jira/browse/INFRA-7179 and
attached the CSV. Do you know what the turnaround time typically is? Please
let me know if I can help in any way.
James
On Wed, Jan 8, 2014 at 1:45 PM, Jake Farrell <jf...@apache.org> wrote:
> The github plugin is not installed in our jira, I would recommend that you
> go with the csv route as Steve mentioned
>
> -Jake
>
>
> On Wed, Jan 8, 2014 at 4:24 PM, Steve Rowe <sa...@gmail.com> wrote:
>
> > Sorry Andy, I don’t know if Infrastructure can/will assist with using
> that
> > plugin, but it can’t hurt to ask, and making an INFRA ticket should work
> > for that.
> >
> > I searched INFRA issues for github issue migration and found none that
> > involved the Atlassian plugin - they all used github CSV export when was
> > then imported to JIRA by Infrastructure (AFAICT):
> >
> > https://issues.apache.org/jira/browse/INFRA-3596
> > https://issues.apache.org/jira/browse/INFRA-3761
> > https://issues.apache.org/jira/browse/INFRA-5951
> >
> > I see you already have the PHOENIX project set up in JIRA (
> > https://issues.apache.org/jira/browse/PHOENIX), so that should simplify
> > the import task whichever way you end up going.
> >
> > Good luck,
> > Steve
> >
> > On Jan 7, 2014, at 3:20 PM, Andrew Purtell <ap...@apache.org> wrote:
> >
> > > So that means we need an INFRA ticket to plug that in and run an
> import?
> > >
> > >
> > > On Mon, Jan 6, 2014 at 4:16 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >
> > >> Atlassian provides a plugin for that:
> > >>
> > >>
> >
> https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-github-plugin
> > >>
> > >>
> > >> On Mon, Jan 6, 2014 at 6:55 PM, James Taylor <ja...@apache.org>
> > >> wrote:
> > >>
> > >>> Hello,
> > >>> Anyone out there know of an automated way of transferring over Github
> > >>> issues to JIRA? We're in the process of transferring over our
> existing
> > >>> Phoenix Github-based open source project to our Apache incubator
> > project
> > >>> and automating the seeding of the initial JIRAs would be very
> helpful.
> > >>> Thanks,
> > >>> James
> > >>>
> > >>
> > >
> > >
> > >
> > > --
> > > Best regards,
> > >
> > > - Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
Re: transferring Github issues to JIRA?
Posted by Andrew Purtell <ap...@apache.org>.
Thanks Jake.
On Wed, Jan 8, 2014 at 1:45 PM, Jake Farrell <jf...@apache.org> wrote:
> The github plugin is not installed in our jira, I would recommend that you
> go with the csv route as Steve mentioned
>
> -Jake
>
>
> On Wed, Jan 8, 2014 at 4:24 PM, Steve Rowe <sa...@gmail.com> wrote:
>
> > Sorry Andy, I don’t know if Infrastructure can/will assist with using
> that
> > plugin, but it can’t hurt to ask, and making an INFRA ticket should work
> > for that.
> >
> > I searched INFRA issues for github issue migration and found none that
> > involved the Atlassian plugin - they all used github CSV export when was
> > then imported to JIRA by Infrastructure (AFAICT):
> >
> > https://issues.apache.org/jira/browse/INFRA-3596
> > https://issues.apache.org/jira/browse/INFRA-3761
> > https://issues.apache.org/jira/browse/INFRA-5951
> >
> > I see you already have the PHOENIX project set up in JIRA (
> > https://issues.apache.org/jira/browse/PHOENIX), so that should simplify
> > the import task whichever way you end up going.
> >
> > Good luck,
> > Steve
> >
> > On Jan 7, 2014, at 3:20 PM, Andrew Purtell <ap...@apache.org> wrote:
> >
> > > So that means we need an INFRA ticket to plug that in and run an
> import?
> > >
> > >
> > > On Mon, Jan 6, 2014 at 4:16 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >
> > >> Atlassian provides a plugin for that:
> > >>
> > >>
> >
> https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-github-plugin
> > >>
> > >>
> > >> On Mon, Jan 6, 2014 at 6:55 PM, James Taylor <ja...@apache.org>
> > >> wrote:
> > >>
> > >>> Hello,
> > >>> Anyone out there know of an automated way of transferring over Github
> > >>> issues to JIRA? We're in the process of transferring over our
> existing
> > >>> Phoenix Github-based open source project to our Apache incubator
> > project
> > >>> and automating the seeding of the initial JIRAs would be very
> helpful.
> > >>> Thanks,
> > >>> James
> > >>>
> > >>
> > >
> > >
> > >
> > > --
> > > Best regards,
> > >
> > > - Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: transferring Github issues to JIRA?
Posted by Jake Farrell <jf...@apache.org>.
The github plugin is not installed in our jira, I would recommend that you
go with the csv route as Steve mentioned
-Jake
On Wed, Jan 8, 2014 at 4:24 PM, Steve Rowe <sa...@gmail.com> wrote:
> Sorry Andy, I don’t know if Infrastructure can/will assist with using that
> plugin, but it can’t hurt to ask, and making an INFRA ticket should work
> for that.
>
> I searched INFRA issues for github issue migration and found none that
> involved the Atlassian plugin - they all used github CSV export when was
> then imported to JIRA by Infrastructure (AFAICT):
>
> https://issues.apache.org/jira/browse/INFRA-3596
> https://issues.apache.org/jira/browse/INFRA-3761
> https://issues.apache.org/jira/browse/INFRA-5951
>
> I see you already have the PHOENIX project set up in JIRA (
> https://issues.apache.org/jira/browse/PHOENIX), so that should simplify
> the import task whichever way you end up going.
>
> Good luck,
> Steve
>
> On Jan 7, 2014, at 3:20 PM, Andrew Purtell <ap...@apache.org> wrote:
>
> > So that means we need an INFRA ticket to plug that in and run an import?
> >
> >
> > On Mon, Jan 6, 2014 at 4:16 PM, Steve Rowe <sa...@gmail.com> wrote:
> >
> >> Atlassian provides a plugin for that:
> >>
> >>
> https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-github-plugin
> >>
> >>
> >> On Mon, Jan 6, 2014 at 6:55 PM, James Taylor <ja...@apache.org>
> >> wrote:
> >>
> >>> Hello,
> >>> Anyone out there know of an automated way of transferring over Github
> >>> issues to JIRA? We're in the process of transferring over our existing
> >>> Phoenix Github-based open source project to our Apache incubator
> project
> >>> and automating the seeding of the initial JIRAs would be very helpful.
> >>> Thanks,
> >>> James
> >>>
> >>
> >
> >
> >
> > --
> > Best regards,
> >
> > - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: transferring Github issues to JIRA?
Posted by Steve Rowe <sa...@gmail.com>.
Sorry Andy, I don’t know if Infrastructure can/will assist with using that plugin, but it can’t hurt to ask, and making an INFRA ticket should work for that.
I searched INFRA issues for github issue migration and found none that involved the Atlassian plugin - they all used github CSV export when was then imported to JIRA by Infrastructure (AFAICT):
https://issues.apache.org/jira/browse/INFRA-3596
https://issues.apache.org/jira/browse/INFRA-3761
https://issues.apache.org/jira/browse/INFRA-5951
I see you already have the PHOENIX project set up in JIRA (https://issues.apache.org/jira/browse/PHOENIX), so that should simplify the import task whichever way you end up going.
Good luck,
Steve
On Jan 7, 2014, at 3:20 PM, Andrew Purtell <ap...@apache.org> wrote:
> So that means we need an INFRA ticket to plug that in and run an import?
>
>
> On Mon, Jan 6, 2014 at 4:16 PM, Steve Rowe <sa...@gmail.com> wrote:
>
>> Atlassian provides a plugin for that:
>>
>> https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-github-plugin
>>
>>
>> On Mon, Jan 6, 2014 at 6:55 PM, James Taylor <ja...@apache.org>
>> wrote:
>>
>>> Hello,
>>> Anyone out there know of an automated way of transferring over Github
>>> issues to JIRA? We're in the process of transferring over our existing
>>> Phoenix Github-based open source project to our Apache incubator project
>>> and automating the seeding of the initial JIRAs would be very helpful.
>>> Thanks,
>>> James
>>>
>>
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: transferring Github issues to JIRA?
Posted by Andrew Purtell <ap...@apache.org>.
So that means we need an INFRA ticket to plug that in and run an import?
On Mon, Jan 6, 2014 at 4:16 PM, Steve Rowe <sa...@gmail.com> wrote:
> Atlassian provides a plugin for that:
>
> https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-github-plugin
>
>
> On Mon, Jan 6, 2014 at 6:55 PM, James Taylor <ja...@apache.org>
> wrote:
>
> > Hello,
> > Anyone out there know of an automated way of transferring over Github
> > issues to JIRA? We're in the process of transferring over our existing
> > Phoenix Github-based open source project to our Apache incubator project
> > and automating the seeding of the initial JIRAs would be very helpful.
> > Thanks,
> > James
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: transferring Github issues to JIRA?
Posted by Steve Rowe <sa...@gmail.com>.
Atlassian provides a plugin for that:
https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-github-plugin
On Mon, Jan 6, 2014 at 6:55 PM, James Taylor <ja...@apache.org> wrote:
> Hello,
> Anyone out there know of an automated way of transferring over Github
> issues to JIRA? We're in the process of transferring over our existing
> Phoenix Github-based open source project to our Apache incubator project
> and automating the seeding of the initial JIRAs would be very helpful.
> Thanks,
> James
>