From derby-dev-return-70421-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Wed Jul 01 13:22:39 2009 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 22600 invoked from network); 1 Jul 2009 13:22:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Jul 2009 13:22:39 -0000 Received: (qmail 1612 invoked by uid 500); 1 Jul 2009 13:22:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 1592 invoked by uid 500); 1 Jul 2009 13:22:50 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 1584 invoked by uid 99); 1 Jul 2009 13:22:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 13:22:49 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [192.18.6.21] (HELO gmp-eb-inf-1.sun.com) (192.18.6.21) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 13:22:39 +0000 Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n61DMIZd020812 for ; Wed, 1 Jul 2009 13:22:18 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KM300C00U4O6200@fe-emea-10.sun.com> for derby-dev@db.apache.org; Wed, 01 Jul 2009 14:22:18 +0100 (BST) Received: from [129.159.139.223] ([unknown] [129.159.139.223]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KM300C4OUH4HE90@fe-emea-10.sun.com> for derby-dev@db.apache.org; Wed, 01 Jul 2009 14:22:16 +0100 (BST) Date: Wed, 01 Jul 2009 15:20:43 +0200 From: Kristian Waagan Subject: Re: Jira field definitions In-reply-to: <4A4B5CDD.1070507@sun.com> Sender: Kristian.Waagan@Sun.COM To: derby-dev@db.apache.org Message-id: <4A4B62AB.4060301@Sun.COM> References: <4A159C28.2000003@sbcglobal.net> <4A15AF13.5000209@sun.com> <4A16ACF7.4070907@sbcglobal.net> <4A3914AF.4050104@sun.com> <4A3FAAD1.5070401@sun.com> <4A3FAE69.4070205@sbcglobal.net> <4A4B5CDD.1070507@sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090505) X-Virus-Checked: Checked by ClamAV on apache.org Rick Hillegas wrote: > Hi Dag, > > Once again, thanks for overhauling our JIRA form. I just want to note > what I think is a welcome divergence from last week's version of your > proposal. I thought that your proposal called for paring back the > legal values of the Issue Type field to Bug, Improvement, Task, and > Sub-task. I see that you have eliminated the last value as well. So > now there are only 3 values: Bug, Improvement, and Task. I think > that's ok because Sub-tasks can be flagged by linking issues together. For clarity, we can still create sub-tasks. What has changed, I guess, is that it can't be done from the main "Create new issue" link any more. For existing issues you can just click "Create sub-task" though. Regards, -- Kristian > > Thanks, > -Rick > > Dag H. Wanvik wrote: >> Another update, folks, the next phase has been completed, Derby now >> uses its own JIRA Issue Type Scheme, which means that the "Wish", "New >> Feature", and "Test" issue types are gone. Old "Test" issues have been >> converted to "Bug" or "Improvement" on a case by case basis, "Wish" >> and "New Feature" have been moved to "Improvement". >> >> Of course I forgot to unclick the "Send email" check-box in one case >> so you have been properly spammed again; sorry! >> >> Dag >> >