Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DAB804E56 for ; Tue, 5 Jul 2011 18:01:42 +0000 (UTC) Received: (qmail 45737 invoked by uid 500); 5 Jul 2011 18:01:42 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 45323 invoked by uid 500); 5 Jul 2011 18:01:41 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 45315 invoked by uid 99); 5 Jul 2011 18:01:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jul 2011 18:01:41 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rabastus@gmail.com designates 209.85.210.175 as permitted sender) Received: from [209.85.210.175] (HELO mail-iy0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jul 2011 18:01:36 +0000 Received: by iym10 with SMTP id 10so5855298iym.6 for ; Tue, 05 Jul 2011 11:01:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=UME7jAMQl3bO5DOl99+/vcwuHUR19/AKtQ8UtYMCVko=; b=J1u5wUBCU42W5eWkSENAWgPz6g7m5CHSHAnnYnWh7dIPps6q9UJJ9IAsvDpkgK0MrD itWEeOPaOmYAIIddHy/pDwUILJOd4EQpO0dzeMGCjVdwNCm5urW6kiMHjufaeICTyux3 iibeDuVuRwhOjthemeg+ZJs8cI2IXNa4Ljt/Y= MIME-Version: 1.0 Received: by 10.42.149.136 with SMTP id w8mr8566537icv.482.1309888876412; Tue, 05 Jul 2011 11:01:16 -0700 (PDT) Sender: rabastus@gmail.com Received: by 10.42.247.193 with HTTP; Tue, 5 Jul 2011 11:01:16 -0700 (PDT) In-Reply-To: <4E134C5E.8050009@gmx.ch> References: <4E13435A.4010407@gmx.ch> <4E134C5E.8050009@gmx.ch> Date: Tue, 5 Jul 2011 14:01:16 -0400 X-Google-Sender-Auth: I0MdbaEdIiE_E8WJY1Jcfm1lYKY Message-ID: Subject: Re: Migration, Bugzilla to JIRA From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jul 5, 2011 at 1:39 PM, Raphael Bircher wrote: > Am 05.07.11 19:12, schrieb Rob Weir: >> >> On Tue, Jul 5, 2011 at 1:01 PM, Raphael Bircher =C2=A0= wrote: >>> >>> Am 05.07.11 18:27, schrieb Rob Weir: >>>> >>>> I'd like to help move this discussion forward. =C2=A0I'm not perceivin= g any >>>> *strong* opinions on the Bugzilla versus JIRA question. =C2=A0But I am >>>> hearing several suggest that JIRA is a better tracker (custom >>>> dashboards in particular were called out). =C2=A0Bugzilla got some nod= s for >>>> the ease of migration and the customization done to the OOo version. >>> >>> Let's wait a little bit longer. The OOo Bugzilla is adapted in same cas= e >>> to >>> the project. First I'like to have a database dump and the used bugzilla >>> templates. So we can find out the difference between normal Bugzilla an= d >>> the >>> OOo Bugzilla. And If we realy want to mofe to JIRA then we should first >>> evaluate the possible problem Areas. >>> >> Is this something that you are working on? >> >> Right now, I'm only exploring feasibility, what is possible. =C2=A0If we >> find that migration to JIRA is feasible, then I'd propose going ahead >> with it. =C2=A0But now I am exploring. =C2=A0But I think this is somethi= ng that >> we can do quickly. =C2=A0It is one of the easier areas to migrate. > > Yes, I working on this at the moment > >>> For my point of view it's not a good idea to setup now all tools. Else = we >>> will maybe run in the problem, that we can't import the old data. >>> >> Our notes crossed, but did you see the my idea of migrating first to a >> clean, uncustomized Bugzilla, and then from there to JIRA? > > No, our Bugzilla is adapted cause the normal bugzilla does not cover all = of > our needs. So we have to look first if JIRA cover's all our needs. It's n= ot > a good Idea to make a desidation about a tool without know, what's our > feature request. (Oh, this tool looks great, let's take this one) > Are these special needs documented someplace? > Bugzilla to Bugzilla sould be not a problem, if we can take over the > adaptions for the OOo Bugzilla > This will probably depend on the nature of the adaptions. Is it just UI? Or does it have DB implications? Is there someone on the project today who maintains the customizations, so, for example, they can be updated when we update JIRA? Or who can fix something if a browser update breaks it? > Bugzilla to JIRA. > > If we like to move to JIRA we should check the flowing first: > > * Cover JIRA all our Features wich we have in Bugzilla? What is actually required versus what is "nice to have"? I don't think that we necessarily must have something identical to what was in the previous OOo installation. I could be proven wrong, but that would require at least some discussion of what Bugzilla does that is: 1) Not doable in JIRA, 2) Cannot be added via customization in JIRA and 3) Is actually necessary for the project. > * Has JIRA the same or better performance? > * How we migrate from Bugzilla to JIRA? Works the migrations tools fine e= tc. > Remember, migrations tools can easely fail, if a tool is adapted. Therefo= r > we have to test it first, and maybe we have to adapt it. > That's why I was suggesting that we migrate to vanilla, uncustomized Bugzilla first. That is more likely to migrate to JIRA without problems. > Greetings Raphael > -- > My private Homepage: http://www.raphaelbircher.ch/ >