You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@visi.com> on 2006/09/19 21:46:53 UTC
Re: Migrating JIRA (was Re: Incubation)
Alright, I downloaded a copy of Jira this weekend and have been
hacking on a jelly script to essentially recreate the issues in a new
Jira. Getting really close but not quite there. Will send more info
later today or tomorrow.
-David
On Aug 30, 2006, at 4:39 PM, Mohammad Nour El-Din wrote:
> Hi Jeff and Jason...
>
> Any one can give me more info about JIRA so I can see if I can help
> or not
> ??? I mean more specifically how to write code to insert into a
> JIRA system
> ???
>
>
>
> On 8/31/06, David Blevins <da...@visi.com> wrote:
>
>>
>> On Aug 30, 2006, at 4:04 PM, Mohammed Nour wrote:
>>
>> > Hi Daves...
>> >
>> > :D, well I am sorry for not being consistent in my name, but the
>> right
>> > pronunciation in Arabic is Mohammad, and as this is the name of our
>> > prophet
>> > I'd like it to be in the right way :D, so I choose Mohammad :),
>> > thanks for
>> > being care to call me with the right name, and I hope I do the same
>> > with you
>> > :).
>>
>> David or Dave is fine for me.
>>
>> > Regarding Jira, who is the expert so I can contact him\her ?
>>
>> Jeff or Jason might be able to give some info. The problem of
>> migrating issues between Jira systems has yet to be solved in
>> general. Jason's serialization idea may or may not be plausible.
>>
>> -David
>>
>> >
>> >
>> > On 8/30/06, David Blevins <da...@visi.com> wrote:
>> >>
>> >> On Aug 30, 2006, at 6:26 AM, Mohammed Nour wrote:
>> >>
>> >> > Hi Daves...
>> >> >
>> >> > Is it possible to export the JIRAs that we want to migrate to
>> some
>> >> > sort of
>> >> > other portable format like XML for example, and then import
>> these
>> >> > JIRAs to
>> >> > the other system, this feature is available in DB2, you can
>> do this
>> >> > with
>> >> > databases, if this is possible so we can export the JIRAs using
>> >> > what ever
>> >> > tool, and then re-import them on the other system without
>> worrying
>> >> > about
>> >> > copying the JIRAs using the APIs of Swizzle and missing the
>> ability
>> >> > to get
>> >> > the info that you told me are going to be missing when we
>> copy the
>> >> > JIRAs
>> >> > using these APIs.
>> >>
>> >> I guess the short answer is, I don't know :) Sorry, not a JIRA
>> >> expert.
>> >>
>> >> On an unrelated note, you patch had "Mohammad" and your emails
>> have
>> >> "Mohammed" with an "e". Which do you prefer?
>> >>
>> >> -David
>> >>
>> >> >
>> >> >
>> >> > On 8/30/06, Mohammed Nour <no...@gmail.com> wrote:
>> >> >
>> >> >> :), actually you closed the door that I was trying to go
>> through,
>> >> >> if Jason
>> >> >> or anybody else can help me more to understand the task so I
>> can
>> >> >> decide if I
>> >> >> can help or not it would be better.
>> >> >>
>> >> >>
>> >> >> On 8/30/06, David Blevins <da...@visi.com> wrote:
>> >> >> >
>> >> >> > On Aug 29, 2006, at 4:04 PM, Mohammed Nour wrote:
>> >> >> >
>> >> >> > > I have build the src code of Swizzle and could run the
>> >> >> JiraExample
>> >> >> > > program,
>> >> >> > > I think I can help but I need more info about what should
>> >> be done
>> >> >> > > exactly.
>> >> >> >
>> >> >> > Jason was talking about a possible way to migrate data stored
>> >> >> > internally in one Jira installation to another Jira
>> >> installation by
>> >> >> > writing some code that would be installed into Jira that
>> would
>> >> >> > serialize the required data from Jira System A then
>> >> deserialize it
>> >> >> > into Jira System B and I guess insert it somehow? Jason
>> is that
>> >> >> > right? It's a bit over my head as I don't have a clue how
>> Jira
>> >> >> works
>> >> >> > internally.
>> >> >> >
>> >> >> > The swizzle stuff I wrote could potentially do a different
>> thing
>> >> >> > which would be to create new Jira Issues in a new Jira
>> System.
>> >> >> We'd
>> >> >> > create one new Jira Issue for each Jira issue in the old Jira
>> >> >> > System. But that's less than optimal as we'd lose all the
>> >> dates,
>> >> >> > links, attachments, etc. Also 50% of our Jira Issues are
>> >> subtasks
>> >> >> > which you *can't* add via the XML-RPC api swizzle uses.
>> >> >> >
>> >> >> > -David
>> >> >> >
>> >> >> > > Thanks and best regards...
>> >> >> > > Mohammad Nour El-Din
>> >> >> > >
>> >> >> > >
>> >> >> > > On 8/30/06, David Blevins <da...@visi.com> wrote:
>> >> >> > >
>> >> >> > >> Anyone have any time to experiment with the serialized
>> object
>> >> >> > >> approach to marshalling data from one confluence
>> install to
>> >> >> the next?
>> >> >> > >>
>> >> >> > >> It'd be a major win.
>> >> >> > >>
>> >> >> > >> -David
>> >> >> > >>
>> >> >> > >> On Jul 20, 2006, at 8:41 PM, David Blevins wrote:
>> >> >> > >>
>> >> >> > >> > I'd certainly love it if we could get that to work.
>> >> >> > >> >
>> >> >> > >> > If we could the migrate the codehaus Jira issues into
>> the
>> >> >> Apache
>> >> >> > >> > jira, then we could finally take all those OpenEJB
>> issues
>> >> >> in the
>> >> >> > >> > Geronimo Jira and move them right into OpenEJB. Same
>> goes
>> >> >> for any
>> >> >> > >> > future OpenEJB issues people file under the Geronimo
>> Jira.
>> >> >> > >> >
>> >> >> > >> > What a dream that would be.
>> >> >> > >> >
>> >> >> > >> > -David
>> >> >> > >> >
>> >> >> > >> >
>> >> >> > >> > On Jul 17, 2006, at 11:22 PM, Henri Yandell wrote:
>> >> >> > >> >
>> >> >> > >> >> Attachments and change history were the two that Jeff
>> >> >> mentioned as
>> >> >> >
>> >> >> > >> >> definitely not being in the xmlrpc/soap interfaces. The
>> >> >> > >> serialization
>> >> >> > >> >> idea is interesting though.
>> >> >> > >> >>
>> >> >> > >> >> Hen
>> >> >> > >> >>
>> >> >> > >> >> On 7/12/06, Jason Dillon <ja...@planet57.com> wrote:
>> >> >> > >> >>> I was under the impression that the SOAP interface for
>> >> JIRA
>> >> >> > >> was much
>> >> >> > >> >>> more feature-rich than the XMLRPC interface... though
>> >> >> probably
>> >> >> > >> still
>> >> >> > >> >>> not enough to copy from instance to instance.
>> >> >> > >> >>>
>> >> >> > >> >>> But, it should be possible to just write a plugin that
>> >> will
>> >> >> > >> expose
>> >> >> > >> >>> the right data... does not need to be a full RPC
>> plugin
>> >> >> either...
>> >> >> > >> >>> could just be to expose a project and the raw issue
>> >> detail
>> >> >> > >> (even as
>> >> >> > >> >>> serialized objects or marshaled w/xstream) to be
>> >> pulled into
>> >> >> > >> another
>> >> >> > >> >>> instance.
>> >> >> > >> >>>
>> >> >> > >> >>> --jason
>> >> >> > >> >>>
>> >> >> > >> >>>
>> >> >> > >> >>> On Jul 12, 2006, at 10:01 PM, David Blevins wrote:
>> >> >> > >> >>>
>> >> >> > >> >>> >
>> >> >> > >> >>> > On Jul 10, 2006, at 10:49 PM, Henri Yandell wrote:
>> >> >> > >> >>> >
>> >> >> > >> >>> >> On 7/10/06, Brett Porter < brett@apache.org> wrote:
>> >> >> > >> >>> >>> On 6/07/2006 9:50 AM, David Blevins wrote:
>> >> >> > >> >>> >>>
>> >> >> > >> >>> >>> > Not sure what is required for JIRA -- I seem to
>> >> recall
>> >> >> > >> >>> >>> > it is a big undertaking.
>> >> >> > >> >>> >>>
>> >> >> > >> >>> >>> You have the following options:
>> >> >> > >> >>> >>> - leave it at Codehaus
>> >> >> > >> >>> >>> - have your own instance running on
>> issues.apache.org
>> >> >> (like
>> >> >> > >> >>> >>> Struts do)
>> >> >> > >> >>> >>> - bribe Atlassian into implementing the merge
>> >> feature.
>> >> >> > >> >>> >>> - start fresh
>> >> >> > >> >>> >>
>> >> >> > >> >>> >> - Hope that Hen finds time to improve the Jira
>> xmlrpc
>> >> >> > >> >>> interface so he
>> >> >> > >> >>> >> can start to write a script to migrate a Jira
>> from one
>> >> >> > >> >>> instance to
>> >> >> > >> >>> >> another. :)
>> >> >> > >> >>> >
>> >> >> > >> >>> > I wrote a java client on top of the xmlrpc
>> interface,
>> >> >> which may
>> >> >> > >> >>> > help you.
>> >> >> > >> >>> >
>> >> >> > >> >>> > http://swizzle.codehaus.org/swizzle-jira/
>> >> >> > >> >>> > http://docs.codehaus.org/display/SWIZZLE/Swizzle
>> +Jira
>> >> >> > >> >>> >
>> >> >> > >> >>> > Never tried to lookup an Issue from one Jira then
>> add
>> >> >> it to
>> >> >> > >> >>> > another. Dunno if it will add all the comments, etc
>> >> that
>> >> >> > >> are in
>> >> >> > >> >>> > the Issue. If so, you might be a for loop + testing
>> >> >> time away
>> >> >> > >> >>> from
>> >> >> > >> >>> > a workable solution
>> >> >> > >> >>> >
>> >> >> > >> >>> > -David
>> >> >> > >> >>> >
>> >> >> > >> >>> >
>> >> >> > >> >>> >
>> >> >> > >> >>>
>> >> >> > >>
>> >> >>
>> >>
>> --------------------------------------------------------------------
>> >> >> > >> >>> -
>> >> >> > >> >>> > To unsubscribe from this list please visit:
>> >> >> > >> >>> >
>> >> >> > >> >>> > http://xircles.codehaus.org/manage_email
>> >> >> > >> >>> >
>> >> >> > >> >>>
>> >> >> > >> >>>
>> >> >> > >> >>>
>> >> >> > >>
>> >> >>
>> >>
>> --------------------------------------------------------------------
>> >> >> > >> >>> -
>> >> >> > >> >>> To unsubscribe from this list please visit:
>> >> >> > >> >>>
>> >> >> > >> >>> http://xircles.codehaus.org/manage_email
>> >> >> > >> >>>
>> >> >> > >> >>>
>> >> >> > >> >>
>> >> >> > >> >>
>> >> >> > >>
>> >> >>
>> >>
>> ---------------------------------------------------------------------
>> >> >> > >> >> To unsubscribe from this list please visit:
>> >> >> > >> >>
>> >> >> > >> >> http://xircles.codehaus.org/manage_email
>> >> >> > >> >>
>> >> >> > >> >
>> >> >> > >> >
>> >> >> > >> >
>> >> >> > >>
>> >> >>
>> >>
>> ---------------------------------------------------------------------
>> >> >> >
>> >> >> > >> > To unsubscribe from this list please visit:
>> >> >> > >> >
>> >> >> > >> > http://xircles.codehaus.org/manage_email
>> >> >> > >> >
>> >> >> > >>
>> >> >> > >>
>> >> >> >
>> >> >> >
>> >> >>
>> >>
>> >>
>>
>>
Re: Migrating JIRA (was Re: Incubation)
Posted by David Blevins <da...@visi.com>.
On Sep 22, 2006, at 10:07 AM, Henri Yandell wrote:
> Can you record the how-to of it all as you go?
Absolutely. I sent Jeff some instructions and examples and then
walked him through it. I'll send you the same info and if you want
to walk through it we can do that too. I'd like to get as many
people kicking the tires as possible.
> I'd like to repeat for struts, roller, cayenne, activemq and any
> others we have out there.
Excellent, that's exactly why I put in the effort. Seemed like it
had been a problem for too long and really needed to be solved.
> Nice work getting this sorted out :)
Thanks. I'll feel more secure in declaring victory once we've gotten
a couple successful migrations done.
-David
> Hen
>
> On 9/22/06, David Blevins <da...@visi.com> wrote:
>> Looks like we are good to go on a Jira to Jira migration. I managed
>> to find a way to do it with lot's of guidance from Jeff. It's
>> completely generic, as I had hoped, and should work for just about
>> any project. Couple limitations: it doesn't support custom fields
>> and it doesn't preserve links between issues. But other than that
>> it's good to go.
>>
>> Jeff Turner was thinking Sunday would be a good time to do our Jira
>> migration as the final step in the migration process is that we need
>> to restart and reindex Jira which will take 20-30 minutes on the
>> Apache Jira.
>>
>> When we do the migration I'll send a note out to the list "Jira
>> Locked" and then make the codehaus jira read-only.
>>
>> -David
>>
>> On Sep 19, 2006, at 12:46 PM, David Blevins wrote:
>>
>> > Alright, I downloaded a copy of Jira this weekend and have been
>> > hacking on a jelly script to essentially recreate the issues in a
>> > new Jira. Getting really close but not quite there. Will send
>> > more info later today or tomorrow.
>> >
>> > -David
>> >
>> > On Aug 30, 2006, at 4:39 PM, Mohammad Nour El-Din wrote:
>> >
>> >> Hi Jeff and Jason...
>> >>
>> >> Any one can give me more info about JIRA so I can see if I can
>> >> help or not
>> >> ??? I mean more specifically how to write code to insert into a
>> >> JIRA system
>> >> ???
>> >>
>> >>
>> >>
>> >> On 8/31/06, David Blevins <da...@visi.com> wrote:
>> >>
>> >>>
>> >>> On Aug 30, 2006, at 4:04 PM, Mohammed Nour wrote:
>> >>>
>> >>> > Hi Daves...
>> >>> >
>> >>> > :D, well I am sorry for not being consistent in my name, but
>> >>> the right
>> >>> > pronunciation in Arabic is Mohammad, and as this is the name of
>> >>> our
>> >>> > prophet
>> >>> > I'd like it to be in the right way :D, so I choose Mohammad :),
>> >>> > thanks for
>> >>> > being care to call me with the right name, and I hope I do the
>> >>> same
>> >>> > with you
>> >>> > :).
>> >>>
>> >>> David or Dave is fine for me.
>> >>>
>> >>> > Regarding Jira, who is the expert so I can contact him\her ?
>> >>>
>> >>> Jeff or Jason might be able to give some info. The problem of
>> >>> migrating issues between Jira systems has yet to be solved in
>> >>> general. Jason's serialization idea may or may not be plausible.
>> >>>
>> >>> -David
>> >>>
>> >>> >
>> >>> >
>> >>> > On 8/30/06, David Blevins <da...@visi.com> wrote:
>> >>> >>
>> >>> >> On Aug 30, 2006, at 6:26 AM, Mohammed Nour wrote:
>> >>> >>
>> >>> >> > Hi Daves...
>> >>> >> >
>> >>> >> > Is it possible to export the JIRAs that we want to migrate
>> >>> to some
>> >>> >> > sort of
>> >>> >> > other portable format like XML for example, and then import
>> >>> these
>> >>> >> > JIRAs to
>> >>> >> > the other system, this feature is available in DB2, you can
>> >>> do this
>> >>> >> > with
>> >>> >> > databases, if this is possible so we can export the JIRAs
>> using
>> >>> >> > what ever
>> >>> >> > tool, and then re-import them on the other system without
>> >>> worrying
>> >>> >> > about
>> >>> >> > copying the JIRAs using the APIs of Swizzle and missing the
>> >>> ability
>> >>> >> > to get
>> >>> >> > the info that you told me are going to be missing when we
>> >>> copy the
>> >>> >> > JIRAs
>> >>> >> > using these APIs.
>> >>> >>
>> >>> >> I guess the short answer is, I don't know :) Sorry, not a
>> JIRA
>> >>> >> expert.
>> >>> >>
>> >>> >> On an unrelated note, you patch had "Mohammad" and your emails
>> >>> have
>> >>> >> "Mohammed" with an "e". Which do you prefer?
>> >>> >>
>> >>> >> -David
>> >>> >>
>> >>> >> >
>> >>> >> >
>> >>> >> > On 8/30/06, Mohammed Nour <no...@gmail.com> wrote:
>> >>> >> >
>> >>> >> >> :), actually you closed the door that I was trying to go
>> >>> through,
>> >>> >> >> if Jason
>> >>> >> >> or anybody else can help me more to understand the task so
>> >>> I can
>> >>> >> >> decide if I
>> >>> >> >> can help or not it would be better.
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> On 8/30/06, David Blevins <da...@visi.com> wrote:
>> >>> >> >> >
>> >>> >> >> > On Aug 29, 2006, at 4:04 PM, Mohammed Nour wrote:
>> >>> >> >> >
>> >>> >> >> > > I have build the src code of Swizzle and could run the
>> >>> >> >> JiraExample
>> >>> >> >> > > program,
>> >>> >> >> > > I think I can help but I need more info about what
>> should
>> >>> >> be done
>> >>> >> >> > > exactly.
>> >>> >> >> >
>> >>> >> >> > Jason was talking about a possible way to migrate data
>> >>> stored
>> >>> >> >> > internally in one Jira installation to another Jira
>> >>> >> installation by
>> >>> >> >> > writing some code that would be installed into Jira that
>> >>> would
>> >>> >> >> > serialize the required data from Jira System A then
>> >>> >> deserialize it
>> >>> >> >> > into Jira System B and I guess insert it somehow? Jason
>> >>> is that
>> >>> >> >> > right? It's a bit over my head as I don't have a clue
>> >>> how Jira
>> >>> >> >> works
>> >>> >> >> > internally.
>> >>> >> >> >
>> >>> >> >> > The swizzle stuff I wrote could potentially do a
>> >>> different thing
>> >>> >> >> > which would be to create new Jira Issues in a new Jira
>> >>> System.
>> >>> >> >> We'd
>> >>> >> >> > create one new Jira Issue for each Jira issue in the old
>> >>> Jira
>> >>> >> >> > System. But that's less than optimal as we'd lose all
>> the
>> >>> >> dates,
>> >>> >> >> > links, attachments, etc. Also 50% of our Jira Issues are
>> >>> >> subtasks
>> >>> >> >> > which you *can't* add via the XML-RPC api swizzle uses.
>> >>> >> >> >
>> >>> >> >> > -David
>> >>> >> >> >
>> >>> >> >> > > Thanks and best regards...
>> >>> >> >> > > Mohammad Nour El-Din
>> >>> >> >> > >
>> >>> >> >> > >
>> >>> >> >> > > On 8/30/06, David Blevins <da...@visi.com>
>> wrote:
>> >>> >> >> > >
>> >>> >> >> > >> Anyone have any time to experiment with the serialized
>> >>> object
>> >>> >> >> > >> approach to marshalling data from one confluence
>> >>> install to
>> >>> >> >> the next?
>> >>> >> >> > >>
>> >>> >> >> > >> It'd be a major win.
>> >>> >> >> > >>
>> >>> >> >> > >> -David
>> >>> >> >> > >>
>> >>> >> >> > >> On Jul 20, 2006, at 8:41 PM, David Blevins wrote:
>> >>> >> >> > >>
>> >>> >> >> > >> > I'd certainly love it if we could get that to work.
>> >>> >> >> > >> >
>> >>> >> >> > >> > If we could the migrate the codehaus Jira issues
>> >>> into the
>> >>> >> >> Apache
>> >>> >> >> > >> > jira, then we could finally take all those OpenEJB
>> >>> issues
>> >>> >> >> in the
>> >>> >> >> > >> > Geronimo Jira and move them right into OpenEJB.
>> >>> Same goes
>> >>> >> >> for any
>> >>> >> >> > >> > future OpenEJB issues people file under the Geronimo
>> >>> Jira.
>> >>> >> >> > >> >
>> >>> >> >> > >> > What a dream that would be.
>> >>> >> >> > >> >
>> >>> >> >> > >> > -David
>> >>> >> >> > >> >
>> >>> >> >> > >> >
>> >>> >> >> > >> > On Jul 17, 2006, at 11:22 PM, Henri Yandell wrote:
>> >>> >> >> > >> >
>> >>> >> >> > >> >> Attachments and change history were the two that
>> Jeff
>> >>> >> >> mentioned as
>> >>> >> >> >
>> >>> >> >> > >> >> definitely not being in the xmlrpc/soap interfaces.
>> >>> The
>> >>> >> >> > >> serialization
>> >>> >> >> > >> >> idea is interesting though.
>> >>> >> >> > >> >>
>> >>> >> >> > >> >> Hen
>> >>> >> >> > >> >>
>> >>> >> >> > >> >> On 7/12/06, Jason Dillon <ja...@planet57.com>
>> wrote:
>> >>> >> >> > >> >>> I was under the impression that the SOAP interface
>> >>> for
>> >>> >> JIRA
>> >>> >> >> > >> was much
>> >>> >> >> > >> >>> more feature-rich than the XMLRPC interface...
>> though
>> >>> >> >> probably
>> >>> >> >> > >> still
>> >>> >> >> > >> >>> not enough to copy from instance to instance.
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>> But, it should be possible to just write a plugin
>> >>> that
>> >>> >> will
>> >>> >> >> > >> expose
>> >>> >> >> > >> >>> the right data... does not need to be a full RPC
>> >>> plugin
>> >>> >> >> either...
>> >>> >> >> > >> >>> could just be to expose a project and the raw
>> issue
>> >>> >> detail
>> >>> >> >> > >> (even as
>> >>> >> >> > >> >>> serialized objects or marshaled w/xstream) to be
>> >>> >> pulled into
>> >>> >> >> > >> another
>> >>> >> >> > >> >>> instance.
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>> --jason
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>> On Jul 12, 2006, at 10:01 PM, David Blevins wrote:
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>> > On Jul 10, 2006, at 10:49 PM, Henri Yandell
>> wrote:
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>> >> On 7/10/06, Brett Porter < brett@apache.org>
>> >>> wrote:
>> >>> >> >> > >> >>> >>> On 6/07/2006 9:50 AM, David Blevins wrote:
>> >>> >> >> > >> >>> >>>
>> >>> >> >> > >> >>> >>> > Not sure what is required for JIRA -- I
>> seem to
>> >>> >> recall
>> >>> >> >> > >> >>> >>> > it is a big undertaking.
>> >>> >> >> > >> >>> >>>
>> >>> >> >> > >> >>> >>> You have the following options:
>> >>> >> >> > >> >>> >>> - leave it at Codehaus
>> >>> >> >> > >> >>> >>> - have your own instance running on
>> >>> issues.apache.org
>> >>> >> >> (like
>> >>> >> >> > >> >>> >>> Struts do)
>> >>> >> >> > >> >>> >>> - bribe Atlassian into implementing the merge
>> >>> >> feature.
>> >>> >> >> > >> >>> >>> - start fresh
>> >>> >> >> > >> >>> >>
>> >>> >> >> > >> >>> >> - Hope that Hen finds time to improve the Jira
>> >>> xmlrpc
>> >>> >> >> > >> >>> interface so he
>> >>> >> >> > >> >>> >> can start to write a script to migrate a Jira
>> >>> from one
>> >>> >> >> > >> >>> instance to
>> >>> >> >> > >> >>> >> another. :)
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>> > I wrote a java client on top of the xmlrpc
>> >>> interface,
>> >>> >> >> which may
>> >>> >> >> > >> >>> > help you.
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>> > http://swizzle.codehaus.org/swizzle-jira/
>> >>> >> >> > >> >>> > http://docs.codehaus.org/display/SWIZZLE/Swizzle
>> >>> +Jira
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>> > Never tried to lookup an Issue from one Jira
>> >>> then add
>> >>> >> >> it to
>> >>> >> >> > >> >>> > another. Dunno if it will add all the comments,
>> >>> etc
>> >>> >> that
>> >>> >> >> > >> are in
>> >>> >> >> > >> >>> > the Issue. If so, you might be a for loop +
>> >>> testing
>> >>> >> >> time away
>> >>> >> >> > >> >>> from
>> >>> >> >> > >> >>> > a workable solution
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>> > -David
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>>
>> >>> >> >> > >>
>> >>> >> >>
>> >>> >>
>> >>>
>> --------------------------------------------------------------------
>> >>> >> >> > >> >>> -
>> >>> >> >> > >> >>> > To unsubscribe from this list please visit:
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>> > http://xircles.codehaus.org/manage_email
>> >>> >> >> > >> >>> >
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>>
>> >>> >> >> > >>
>> >>> >> >>
>> >>> >>
>> >>>
>> --------------------------------------------------------------------
>> >>> >> >> > >> >>> -
>> >>> >> >> > >> >>> To unsubscribe from this list please visit:
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>> http://xircles.codehaus.org/manage_email
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>>
>> >>> >> >> > >> >>
>> >>> >> >> > >> >>
>> >>> >> >> > >>
>> >>> >> >>
>> >>> >>
>> >>>
>> --------------------------------------------------------------------
>> >>> -
>> >>> >> >> > >> >> To unsubscribe from this list please visit:
>> >>> >> >> > >> >>
>> >>> >> >> > >> >> http://xircles.codehaus.org/manage_email
>> >>> >> >> > >> >>
>> >>> >> >> > >> >
>> >>> >> >> > >> >
>> >>> >> >> > >> >
>> >>> >> >> > >>
>> >>> >> >>
>> >>> >>
>> >>>
>> --------------------------------------------------------------------
>> >>> -
>> >>> >> >> >
>> >>> >> >> > >> > To unsubscribe from this list please visit:
>> >>> >> >> > >> >
>> >>> >> >> > >> > http://xircles.codehaus.org/manage_email
>> >>> >> >> > >> >
>> >>> >> >> > >>
>> >>> >> >> > >>
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >>
>> >>> >>
>> >>> >>
>> >>>
>> >>>
>> >
>>
>>
>
Re: Migrating JIRA (was Re: Incubation)
Posted by Henri Yandell <fl...@gmail.com>.
Can you record the how-to of it all as you go?
I'd like to repeat for struts, roller, cayenne, activemq and any
others we have out there.
Nice work getting this sorted out :)
Hen
On 9/22/06, David Blevins <da...@visi.com> wrote:
> Looks like we are good to go on a Jira to Jira migration. I managed
> to find a way to do it with lot's of guidance from Jeff. It's
> completely generic, as I had hoped, and should work for just about
> any project. Couple limitations: it doesn't support custom fields
> and it doesn't preserve links between issues. But other than that
> it's good to go.
>
> Jeff Turner was thinking Sunday would be a good time to do our Jira
> migration as the final step in the migration process is that we need
> to restart and reindex Jira which will take 20-30 minutes on the
> Apache Jira.
>
> When we do the migration I'll send a note out to the list "Jira
> Locked" and then make the codehaus jira read-only.
>
> -David
>
> On Sep 19, 2006, at 12:46 PM, David Blevins wrote:
>
> > Alright, I downloaded a copy of Jira this weekend and have been
> > hacking on a jelly script to essentially recreate the issues in a
> > new Jira. Getting really close but not quite there. Will send
> > more info later today or tomorrow.
> >
> > -David
> >
> > On Aug 30, 2006, at 4:39 PM, Mohammad Nour El-Din wrote:
> >
> >> Hi Jeff and Jason...
> >>
> >> Any one can give me more info about JIRA so I can see if I can
> >> help or not
> >> ??? I mean more specifically how to write code to insert into a
> >> JIRA system
> >> ???
> >>
> >>
> >>
> >> On 8/31/06, David Blevins <da...@visi.com> wrote:
> >>
> >>>
> >>> On Aug 30, 2006, at 4:04 PM, Mohammed Nour wrote:
> >>>
> >>> > Hi Daves...
> >>> >
> >>> > :D, well I am sorry for not being consistent in my name, but
> >>> the right
> >>> > pronunciation in Arabic is Mohammad, and as this is the name of
> >>> our
> >>> > prophet
> >>> > I'd like it to be in the right way :D, so I choose Mohammad :),
> >>> > thanks for
> >>> > being care to call me with the right name, and I hope I do the
> >>> same
> >>> > with you
> >>> > :).
> >>>
> >>> David or Dave is fine for me.
> >>>
> >>> > Regarding Jira, who is the expert so I can contact him\her ?
> >>>
> >>> Jeff or Jason might be able to give some info. The problem of
> >>> migrating issues between Jira systems has yet to be solved in
> >>> general. Jason's serialization idea may or may not be plausible.
> >>>
> >>> -David
> >>>
> >>> >
> >>> >
> >>> > On 8/30/06, David Blevins <da...@visi.com> wrote:
> >>> >>
> >>> >> On Aug 30, 2006, at 6:26 AM, Mohammed Nour wrote:
> >>> >>
> >>> >> > Hi Daves...
> >>> >> >
> >>> >> > Is it possible to export the JIRAs that we want to migrate
> >>> to some
> >>> >> > sort of
> >>> >> > other portable format like XML for example, and then import
> >>> these
> >>> >> > JIRAs to
> >>> >> > the other system, this feature is available in DB2, you can
> >>> do this
> >>> >> > with
> >>> >> > databases, if this is possible so we can export the JIRAs using
> >>> >> > what ever
> >>> >> > tool, and then re-import them on the other system without
> >>> worrying
> >>> >> > about
> >>> >> > copying the JIRAs using the APIs of Swizzle and missing the
> >>> ability
> >>> >> > to get
> >>> >> > the info that you told me are going to be missing when we
> >>> copy the
> >>> >> > JIRAs
> >>> >> > using these APIs.
> >>> >>
> >>> >> I guess the short answer is, I don't know :) Sorry, not a JIRA
> >>> >> expert.
> >>> >>
> >>> >> On an unrelated note, you patch had "Mohammad" and your emails
> >>> have
> >>> >> "Mohammed" with an "e". Which do you prefer?
> >>> >>
> >>> >> -David
> >>> >>
> >>> >> >
> >>> >> >
> >>> >> > On 8/30/06, Mohammed Nour <no...@gmail.com> wrote:
> >>> >> >
> >>> >> >> :), actually you closed the door that I was trying to go
> >>> through,
> >>> >> >> if Jason
> >>> >> >> or anybody else can help me more to understand the task so
> >>> I can
> >>> >> >> decide if I
> >>> >> >> can help or not it would be better.
> >>> >> >>
> >>> >> >>
> >>> >> >> On 8/30/06, David Blevins <da...@visi.com> wrote:
> >>> >> >> >
> >>> >> >> > On Aug 29, 2006, at 4:04 PM, Mohammed Nour wrote:
> >>> >> >> >
> >>> >> >> > > I have build the src code of Swizzle and could run the
> >>> >> >> JiraExample
> >>> >> >> > > program,
> >>> >> >> > > I think I can help but I need more info about what should
> >>> >> be done
> >>> >> >> > > exactly.
> >>> >> >> >
> >>> >> >> > Jason was talking about a possible way to migrate data
> >>> stored
> >>> >> >> > internally in one Jira installation to another Jira
> >>> >> installation by
> >>> >> >> > writing some code that would be installed into Jira that
> >>> would
> >>> >> >> > serialize the required data from Jira System A then
> >>> >> deserialize it
> >>> >> >> > into Jira System B and I guess insert it somehow? Jason
> >>> is that
> >>> >> >> > right? It's a bit over my head as I don't have a clue
> >>> how Jira
> >>> >> >> works
> >>> >> >> > internally.
> >>> >> >> >
> >>> >> >> > The swizzle stuff I wrote could potentially do a
> >>> different thing
> >>> >> >> > which would be to create new Jira Issues in a new Jira
> >>> System.
> >>> >> >> We'd
> >>> >> >> > create one new Jira Issue for each Jira issue in the old
> >>> Jira
> >>> >> >> > System. But that's less than optimal as we'd lose all the
> >>> >> dates,
> >>> >> >> > links, attachments, etc. Also 50% of our Jira Issues are
> >>> >> subtasks
> >>> >> >> > which you *can't* add via the XML-RPC api swizzle uses.
> >>> >> >> >
> >>> >> >> > -David
> >>> >> >> >
> >>> >> >> > > Thanks and best regards...
> >>> >> >> > > Mohammad Nour El-Din
> >>> >> >> > >
> >>> >> >> > >
> >>> >> >> > > On 8/30/06, David Blevins <da...@visi.com> wrote:
> >>> >> >> > >
> >>> >> >> > >> Anyone have any time to experiment with the serialized
> >>> object
> >>> >> >> > >> approach to marshalling data from one confluence
> >>> install to
> >>> >> >> the next?
> >>> >> >> > >>
> >>> >> >> > >> It'd be a major win.
> >>> >> >> > >>
> >>> >> >> > >> -David
> >>> >> >> > >>
> >>> >> >> > >> On Jul 20, 2006, at 8:41 PM, David Blevins wrote:
> >>> >> >> > >>
> >>> >> >> > >> > I'd certainly love it if we could get that to work.
> >>> >> >> > >> >
> >>> >> >> > >> > If we could the migrate the codehaus Jira issues
> >>> into the
> >>> >> >> Apache
> >>> >> >> > >> > jira, then we could finally take all those OpenEJB
> >>> issues
> >>> >> >> in the
> >>> >> >> > >> > Geronimo Jira and move them right into OpenEJB.
> >>> Same goes
> >>> >> >> for any
> >>> >> >> > >> > future OpenEJB issues people file under the Geronimo
> >>> Jira.
> >>> >> >> > >> >
> >>> >> >> > >> > What a dream that would be.
> >>> >> >> > >> >
> >>> >> >> > >> > -David
> >>> >> >> > >> >
> >>> >> >> > >> >
> >>> >> >> > >> > On Jul 17, 2006, at 11:22 PM, Henri Yandell wrote:
> >>> >> >> > >> >
> >>> >> >> > >> >> Attachments and change history were the two that Jeff
> >>> >> >> mentioned as
> >>> >> >> >
> >>> >> >> > >> >> definitely not being in the xmlrpc/soap interfaces.
> >>> The
> >>> >> >> > >> serialization
> >>> >> >> > >> >> idea is interesting though.
> >>> >> >> > >> >>
> >>> >> >> > >> >> Hen
> >>> >> >> > >> >>
> >>> >> >> > >> >> On 7/12/06, Jason Dillon <ja...@planet57.com> wrote:
> >>> >> >> > >> >>> I was under the impression that the SOAP interface
> >>> for
> >>> >> JIRA
> >>> >> >> > >> was much
> >>> >> >> > >> >>> more feature-rich than the XMLRPC interface... though
> >>> >> >> probably
> >>> >> >> > >> still
> >>> >> >> > >> >>> not enough to copy from instance to instance.
> >>> >> >> > >> >>>
> >>> >> >> > >> >>> But, it should be possible to just write a plugin
> >>> that
> >>> >> will
> >>> >> >> > >> expose
> >>> >> >> > >> >>> the right data... does not need to be a full RPC
> >>> plugin
> >>> >> >> either...
> >>> >> >> > >> >>> could just be to expose a project and the raw issue
> >>> >> detail
> >>> >> >> > >> (even as
> >>> >> >> > >> >>> serialized objects or marshaled w/xstream) to be
> >>> >> pulled into
> >>> >> >> > >> another
> >>> >> >> > >> >>> instance.
> >>> >> >> > >> >>>
> >>> >> >> > >> >>> --jason
> >>> >> >> > >> >>>
> >>> >> >> > >> >>>
> >>> >> >> > >> >>> On Jul 12, 2006, at 10:01 PM, David Blevins wrote:
> >>> >> >> > >> >>>
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>> > On Jul 10, 2006, at 10:49 PM, Henri Yandell wrote:
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>> >> On 7/10/06, Brett Porter < brett@apache.org>
> >>> wrote:
> >>> >> >> > >> >>> >>> On 6/07/2006 9:50 AM, David Blevins wrote:
> >>> >> >> > >> >>> >>>
> >>> >> >> > >> >>> >>> > Not sure what is required for JIRA -- I seem to
> >>> >> recall
> >>> >> >> > >> >>> >>> > it is a big undertaking.
> >>> >> >> > >> >>> >>>
> >>> >> >> > >> >>> >>> You have the following options:
> >>> >> >> > >> >>> >>> - leave it at Codehaus
> >>> >> >> > >> >>> >>> - have your own instance running on
> >>> issues.apache.org
> >>> >> >> (like
> >>> >> >> > >> >>> >>> Struts do)
> >>> >> >> > >> >>> >>> - bribe Atlassian into implementing the merge
> >>> >> feature.
> >>> >> >> > >> >>> >>> - start fresh
> >>> >> >> > >> >>> >>
> >>> >> >> > >> >>> >> - Hope that Hen finds time to improve the Jira
> >>> xmlrpc
> >>> >> >> > >> >>> interface so he
> >>> >> >> > >> >>> >> can start to write a script to migrate a Jira
> >>> from one
> >>> >> >> > >> >>> instance to
> >>> >> >> > >> >>> >> another. :)
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>> > I wrote a java client on top of the xmlrpc
> >>> interface,
> >>> >> >> which may
> >>> >> >> > >> >>> > help you.
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>> > http://swizzle.codehaus.org/swizzle-jira/
> >>> >> >> > >> >>> > http://docs.codehaus.org/display/SWIZZLE/Swizzle
> >>> +Jira
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>> > Never tried to lookup an Issue from one Jira
> >>> then add
> >>> >> >> it to
> >>> >> >> > >> >>> > another. Dunno if it will add all the comments,
> >>> etc
> >>> >> that
> >>> >> >> > >> are in
> >>> >> >> > >> >>> > the Issue. If so, you might be a for loop +
> >>> testing
> >>> >> >> time away
> >>> >> >> > >> >>> from
> >>> >> >> > >> >>> > a workable solution
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>> > -David
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>>
> >>> >> >> > >>
> >>> >> >>
> >>> >>
> >>> --------------------------------------------------------------------
> >>> >> >> > >> >>> -
> >>> >> >> > >> >>> > To unsubscribe from this list please visit:
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>> > http://xircles.codehaus.org/manage_email
> >>> >> >> > >> >>> >
> >>> >> >> > >> >>>
> >>> >> >> > >> >>>
> >>> >> >> > >> >>>
> >>> >> >> > >>
> >>> >> >>
> >>> >>
> >>> --------------------------------------------------------------------
> >>> >> >> > >> >>> -
> >>> >> >> > >> >>> To unsubscribe from this list please visit:
> >>> >> >> > >> >>>
> >>> >> >> > >> >>> http://xircles.codehaus.org/manage_email
> >>> >> >> > >> >>>
> >>> >> >> > >> >>>
> >>> >> >> > >> >>
> >>> >> >> > >> >>
> >>> >> >> > >>
> >>> >> >>
> >>> >>
> >>> --------------------------------------------------------------------
> >>> -
> >>> >> >> > >> >> To unsubscribe from this list please visit:
> >>> >> >> > >> >>
> >>> >> >> > >> >> http://xircles.codehaus.org/manage_email
> >>> >> >> > >> >>
> >>> >> >> > >> >
> >>> >> >> > >> >
> >>> >> >> > >> >
> >>> >> >> > >>
> >>> >> >>
> >>> >>
> >>> --------------------------------------------------------------------
> >>> -
> >>> >> >> >
> >>> >> >> > >> > To unsubscribe from this list please visit:
> >>> >> >> > >> >
> >>> >> >> > >> > http://xircles.codehaus.org/manage_email
> >>> >> >> > >> >
> >>> >> >> > >>
> >>> >> >> > >>
> >>> >> >> >
> >>> >> >> >
> >>> >> >>
> >>> >>
> >>> >>
> >>>
> >>>
> >
>
>
Re: Migrating JIRA (was Re: Incubation)
Posted by David Blevins <da...@visi.com>.
Looks like we are good to go on a Jira to Jira migration. I managed
to find a way to do it with lot's of guidance from Jeff. It's
completely generic, as I had hoped, and should work for just about
any project. Couple limitations: it doesn't support custom fields
and it doesn't preserve links between issues. But other than that
it's good to go.
Jeff Turner was thinking Sunday would be a good time to do our Jira
migration as the final step in the migration process is that we need
to restart and reindex Jira which will take 20-30 minutes on the
Apache Jira.
When we do the migration I'll send a note out to the list "Jira
Locked" and then make the codehaus jira read-only.
-David
On Sep 19, 2006, at 12:46 PM, David Blevins wrote:
> Alright, I downloaded a copy of Jira this weekend and have been
> hacking on a jelly script to essentially recreate the issues in a
> new Jira. Getting really close but not quite there. Will send
> more info later today or tomorrow.
>
> -David
>
> On Aug 30, 2006, at 4:39 PM, Mohammad Nour El-Din wrote:
>
>> Hi Jeff and Jason...
>>
>> Any one can give me more info about JIRA so I can see if I can
>> help or not
>> ??? I mean more specifically how to write code to insert into a
>> JIRA system
>> ???
>>
>>
>>
>> On 8/31/06, David Blevins <da...@visi.com> wrote:
>>
>>>
>>> On Aug 30, 2006, at 4:04 PM, Mohammed Nour wrote:
>>>
>>> > Hi Daves...
>>> >
>>> > :D, well I am sorry for not being consistent in my name, but
>>> the right
>>> > pronunciation in Arabic is Mohammad, and as this is the name of
>>> our
>>> > prophet
>>> > I'd like it to be in the right way :D, so I choose Mohammad :),
>>> > thanks for
>>> > being care to call me with the right name, and I hope I do the
>>> same
>>> > with you
>>> > :).
>>>
>>> David or Dave is fine for me.
>>>
>>> > Regarding Jira, who is the expert so I can contact him\her ?
>>>
>>> Jeff or Jason might be able to give some info. The problem of
>>> migrating issues between Jira systems has yet to be solved in
>>> general. Jason's serialization idea may or may not be plausible.
>>>
>>> -David
>>>
>>> >
>>> >
>>> > On 8/30/06, David Blevins <da...@visi.com> wrote:
>>> >>
>>> >> On Aug 30, 2006, at 6:26 AM, Mohammed Nour wrote:
>>> >>
>>> >> > Hi Daves...
>>> >> >
>>> >> > Is it possible to export the JIRAs that we want to migrate
>>> to some
>>> >> > sort of
>>> >> > other portable format like XML for example, and then import
>>> these
>>> >> > JIRAs to
>>> >> > the other system, this feature is available in DB2, you can
>>> do this
>>> >> > with
>>> >> > databases, if this is possible so we can export the JIRAs using
>>> >> > what ever
>>> >> > tool, and then re-import them on the other system without
>>> worrying
>>> >> > about
>>> >> > copying the JIRAs using the APIs of Swizzle and missing the
>>> ability
>>> >> > to get
>>> >> > the info that you told me are going to be missing when we
>>> copy the
>>> >> > JIRAs
>>> >> > using these APIs.
>>> >>
>>> >> I guess the short answer is, I don't know :) Sorry, not a JIRA
>>> >> expert.
>>> >>
>>> >> On an unrelated note, you patch had "Mohammad" and your emails
>>> have
>>> >> "Mohammed" with an "e". Which do you prefer?
>>> >>
>>> >> -David
>>> >>
>>> >> >
>>> >> >
>>> >> > On 8/30/06, Mohammed Nour <no...@gmail.com> wrote:
>>> >> >
>>> >> >> :), actually you closed the door that I was trying to go
>>> through,
>>> >> >> if Jason
>>> >> >> or anybody else can help me more to understand the task so
>>> I can
>>> >> >> decide if I
>>> >> >> can help or not it would be better.
>>> >> >>
>>> >> >>
>>> >> >> On 8/30/06, David Blevins <da...@visi.com> wrote:
>>> >> >> >
>>> >> >> > On Aug 29, 2006, at 4:04 PM, Mohammed Nour wrote:
>>> >> >> >
>>> >> >> > > I have build the src code of Swizzle and could run the
>>> >> >> JiraExample
>>> >> >> > > program,
>>> >> >> > > I think I can help but I need more info about what should
>>> >> be done
>>> >> >> > > exactly.
>>> >> >> >
>>> >> >> > Jason was talking about a possible way to migrate data
>>> stored
>>> >> >> > internally in one Jira installation to another Jira
>>> >> installation by
>>> >> >> > writing some code that would be installed into Jira that
>>> would
>>> >> >> > serialize the required data from Jira System A then
>>> >> deserialize it
>>> >> >> > into Jira System B and I guess insert it somehow? Jason
>>> is that
>>> >> >> > right? It's a bit over my head as I don't have a clue
>>> how Jira
>>> >> >> works
>>> >> >> > internally.
>>> >> >> >
>>> >> >> > The swizzle stuff I wrote could potentially do a
>>> different thing
>>> >> >> > which would be to create new Jira Issues in a new Jira
>>> System.
>>> >> >> We'd
>>> >> >> > create one new Jira Issue for each Jira issue in the old
>>> Jira
>>> >> >> > System. But that's less than optimal as we'd lose all the
>>> >> dates,
>>> >> >> > links, attachments, etc. Also 50% of our Jira Issues are
>>> >> subtasks
>>> >> >> > which you *can't* add via the XML-RPC api swizzle uses.
>>> >> >> >
>>> >> >> > -David
>>> >> >> >
>>> >> >> > > Thanks and best regards...
>>> >> >> > > Mohammad Nour El-Din
>>> >> >> > >
>>> >> >> > >
>>> >> >> > > On 8/30/06, David Blevins <da...@visi.com> wrote:
>>> >> >> > >
>>> >> >> > >> Anyone have any time to experiment with the serialized
>>> object
>>> >> >> > >> approach to marshalling data from one confluence
>>> install to
>>> >> >> the next?
>>> >> >> > >>
>>> >> >> > >> It'd be a major win.
>>> >> >> > >>
>>> >> >> > >> -David
>>> >> >> > >>
>>> >> >> > >> On Jul 20, 2006, at 8:41 PM, David Blevins wrote:
>>> >> >> > >>
>>> >> >> > >> > I'd certainly love it if we could get that to work.
>>> >> >> > >> >
>>> >> >> > >> > If we could the migrate the codehaus Jira issues
>>> into the
>>> >> >> Apache
>>> >> >> > >> > jira, then we could finally take all those OpenEJB
>>> issues
>>> >> >> in the
>>> >> >> > >> > Geronimo Jira and move them right into OpenEJB.
>>> Same goes
>>> >> >> for any
>>> >> >> > >> > future OpenEJB issues people file under the Geronimo
>>> Jira.
>>> >> >> > >> >
>>> >> >> > >> > What a dream that would be.
>>> >> >> > >> >
>>> >> >> > >> > -David
>>> >> >> > >> >
>>> >> >> > >> >
>>> >> >> > >> > On Jul 17, 2006, at 11:22 PM, Henri Yandell wrote:
>>> >> >> > >> >
>>> >> >> > >> >> Attachments and change history were the two that Jeff
>>> >> >> mentioned as
>>> >> >> >
>>> >> >> > >> >> definitely not being in the xmlrpc/soap interfaces.
>>> The
>>> >> >> > >> serialization
>>> >> >> > >> >> idea is interesting though.
>>> >> >> > >> >>
>>> >> >> > >> >> Hen
>>> >> >> > >> >>
>>> >> >> > >> >> On 7/12/06, Jason Dillon <ja...@planet57.com> wrote:
>>> >> >> > >> >>> I was under the impression that the SOAP interface
>>> for
>>> >> JIRA
>>> >> >> > >> was much
>>> >> >> > >> >>> more feature-rich than the XMLRPC interface... though
>>> >> >> probably
>>> >> >> > >> still
>>> >> >> > >> >>> not enough to copy from instance to instance.
>>> >> >> > >> >>>
>>> >> >> > >> >>> But, it should be possible to just write a plugin
>>> that
>>> >> will
>>> >> >> > >> expose
>>> >> >> > >> >>> the right data... does not need to be a full RPC
>>> plugin
>>> >> >> either...
>>> >> >> > >> >>> could just be to expose a project and the raw issue
>>> >> detail
>>> >> >> > >> (even as
>>> >> >> > >> >>> serialized objects or marshaled w/xstream) to be
>>> >> pulled into
>>> >> >> > >> another
>>> >> >> > >> >>> instance.
>>> >> >> > >> >>>
>>> >> >> > >> >>> --jason
>>> >> >> > >> >>>
>>> >> >> > >> >>>
>>> >> >> > >> >>> On Jul 12, 2006, at 10:01 PM, David Blevins wrote:
>>> >> >> > >> >>>
>>> >> >> > >> >>> >
>>> >> >> > >> >>> > On Jul 10, 2006, at 10:49 PM, Henri Yandell wrote:
>>> >> >> > >> >>> >
>>> >> >> > >> >>> >> On 7/10/06, Brett Porter < brett@apache.org>
>>> wrote:
>>> >> >> > >> >>> >>> On 6/07/2006 9:50 AM, David Blevins wrote:
>>> >> >> > >> >>> >>>
>>> >> >> > >> >>> >>> > Not sure what is required for JIRA -- I seem to
>>> >> recall
>>> >> >> > >> >>> >>> > it is a big undertaking.
>>> >> >> > >> >>> >>>
>>> >> >> > >> >>> >>> You have the following options:
>>> >> >> > >> >>> >>> - leave it at Codehaus
>>> >> >> > >> >>> >>> - have your own instance running on
>>> issues.apache.org
>>> >> >> (like
>>> >> >> > >> >>> >>> Struts do)
>>> >> >> > >> >>> >>> - bribe Atlassian into implementing the merge
>>> >> feature.
>>> >> >> > >> >>> >>> - start fresh
>>> >> >> > >> >>> >>
>>> >> >> > >> >>> >> - Hope that Hen finds time to improve the Jira
>>> xmlrpc
>>> >> >> > >> >>> interface so he
>>> >> >> > >> >>> >> can start to write a script to migrate a Jira
>>> from one
>>> >> >> > >> >>> instance to
>>> >> >> > >> >>> >> another. :)
>>> >> >> > >> >>> >
>>> >> >> > >> >>> > I wrote a java client on top of the xmlrpc
>>> interface,
>>> >> >> which may
>>> >> >> > >> >>> > help you.
>>> >> >> > >> >>> >
>>> >> >> > >> >>> > http://swizzle.codehaus.org/swizzle-jira/
>>> >> >> > >> >>> > http://docs.codehaus.org/display/SWIZZLE/Swizzle
>>> +Jira
>>> >> >> > >> >>> >
>>> >> >> > >> >>> > Never tried to lookup an Issue from one Jira
>>> then add
>>> >> >> it to
>>> >> >> > >> >>> > another. Dunno if it will add all the comments,
>>> etc
>>> >> that
>>> >> >> > >> are in
>>> >> >> > >> >>> > the Issue. If so, you might be a for loop +
>>> testing
>>> >> >> time away
>>> >> >> > >> >>> from
>>> >> >> > >> >>> > a workable solution
>>> >> >> > >> >>> >
>>> >> >> > >> >>> > -David
>>> >> >> > >> >>> >
>>> >> >> > >> >>> >
>>> >> >> > >> >>> >
>>> >> >> > >> >>>
>>> >> >> > >>
>>> >> >>
>>> >>
>>> --------------------------------------------------------------------
>>> >> >> > >> >>> -
>>> >> >> > >> >>> > To unsubscribe from this list please visit:
>>> >> >> > >> >>> >
>>> >> >> > >> >>> > http://xircles.codehaus.org/manage_email
>>> >> >> > >> >>> >
>>> >> >> > >> >>>
>>> >> >> > >> >>>
>>> >> >> > >> >>>
>>> >> >> > >>
>>> >> >>
>>> >>
>>> --------------------------------------------------------------------
>>> >> >> > >> >>> -
>>> >> >> > >> >>> To unsubscribe from this list please visit:
>>> >> >> > >> >>>
>>> >> >> > >> >>> http://xircles.codehaus.org/manage_email
>>> >> >> > >> >>>
>>> >> >> > >> >>>
>>> >> >> > >> >>
>>> >> >> > >> >>
>>> >> >> > >>
>>> >> >>
>>> >>
>>> --------------------------------------------------------------------
>>> -
>>> >> >> > >> >> To unsubscribe from this list please visit:
>>> >> >> > >> >>
>>> >> >> > >> >> http://xircles.codehaus.org/manage_email
>>> >> >> > >> >>
>>> >> >> > >> >
>>> >> >> > >> >
>>> >> >> > >> >
>>> >> >> > >>
>>> >> >>
>>> >>
>>> --------------------------------------------------------------------
>>> -
>>> >> >> >
>>> >> >> > >> > To unsubscribe from this list please visit:
>>> >> >> > >> >
>>> >> >> > >> > http://xircles.codehaus.org/manage_email
>>> >> >> > >> >
>>> >> >> > >>
>>> >> >> > >>
>>> >> >> >
>>> >> >> >
>>> >> >>
>>> >>
>>> >>
>>>
>>>
>