Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 46639 invoked from network); 27 Jan 2007 14:13:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jan 2007 14:13:37 -0000 Received: (qmail 22839 invoked by uid 500); 27 Jan 2007 14:13:37 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 22789 invoked by uid 500); 27 Jan 2007 14:13:37 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 22778 invoked by uid 99); 27 Jan 2007 14:13:37 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jan 2007 06:13:37 -0800 X-ASF-Spam-Status: No, hits=3.5 required=10.0 tests=FROM_HAS_MIXED_NUMS,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of c1vamsi1c@gmail.com designates 64.233.182.189 as permitted sender) Received: from [64.233.182.189] (HELO nf-out-0910.google.com) (64.233.182.189) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jan 2007 06:13:28 -0800 Received: by nf-out-0910.google.com with SMTP id m19so1401447nfc for ; Sat, 27 Jan 2007 06:13:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=OgTMfqiZ6k3XiNwgNs4BklGQamI9Rqj/B+kI1mJmIHa0KL6tHVHMoXwRFHYu42zRCVm89WeKbRIo2J0wNdLzSgidGBgYcs9sOfaW/6zD2V4wp6ppAUP+ghDDA8DZkzBN84XvrCWigePtJbydCA1Gidwuvfu6QcRyeA+AHOiLRV4= Received: by 10.49.64.18 with SMTP id r18mr6924387nfk.1169907186892; Sat, 27 Jan 2007 06:13:06 -0800 (PST) Received: by 10.49.11.8 with HTTP; Sat, 27 Jan 2007 06:13:05 -0800 (PST) Message-ID: <22d56c4d0701270613qcb8d60cnaa22c51110cde1b@mail.gmail.com> Date: Sat, 27 Jan 2007 19:43:05 +0530 From: "Vamsavardhana Reddy" To: dev@geronimo.apache.org Subject: Re: Using JIRA In-Reply-To: <45B7B315.3070501@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_227825_6323496.1169907185970" References: <45AF8066.2090705@gmail.com> <45B7B315.3070501@yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_227825_6323496.1169907185970 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I observed that a JIRA will show up in "Patch Availble" only if it is marked as improvement and Begin RTC review is clicked. Vamsi On 1/25/07, Donald Woods wrote: > > Has anyone noticed that the JIRA Project Summary - Patch Available count > is not correct? > https://issues.apache.org/jira/browse/GERONIMO > Currently, it only shows 4 issues with patches, but there are - > 1.1.2 - 1 > 1.2 - 1 > 1.x - 2 > M2 - 4 > Beta1 - 2 > 2.0 - 12 > Wish - 6 > Verif - 1 > Unsch - 28 > So, why isn't the count showing 57 instead? > It seems to only be counting the ones that have Status=Patch Available > and ignoring those with Patch Info=Patch Available. > > > -Donald > > Hernan Cunico wrote: > > Howdy, > > it may sound weird asking this now but I'm either creating JIRAs the > > wrong way or we are not displaying the all the info in > > http://issues.apache.org/jira/browse/geronimo (or I just don't know how > > to read it) > > > > On the JIRA front page for GERONIMO you can see open issues due to be > > fixed per version. > > When I create a JIRA for a specific version I normally specify the > > "affected version" (let's say 2.0-M2) in the *Affects Version/s:* box > > and leave the *Fix Version/s:* empty as I don't really know for sure > > when that issue is going to be fixed unless I am the assignee. > > > > This issue I just created does not get listed (counted actually) for > > that particular version in the project's JIRA home page. > > > > Is this query is automatically provided by JIRA or we can customize it > > to show the affected version instead? > > At this particular point in time the actual setting show 5 open issues, > > if we could change it to affected versions it would show 16. > > > > Does this make any sense at all? > > > > Again, it might be just me not really understanding how to use JIRAs. > > > > Comments appreciated > > > > Cheers! > > Hernan > > > > > > > > > ------=_Part_227825_6323496.1169907185970 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I observed that a JIRA will show up in "Patch Availble" only if it is marked as improvement and Begin RTC review is clicked.

Vamsi

On 1/25/07, Donald Woods <drw_web@yahoo.com> wrote:
Has anyone noticed that the JIRA Project Summary - Patch Available count
is not correct?
        https://issues.apache.org/jira/browse/GERONIMO
Currently, it only shows 4 issues with patches, but there are -
        1.1.2   - 1
        1.2     - 1
        1.x     - 2
        M2      - 4
        Beta1   - 2
        2.0     - 12
        Wish    - 6
        Verif   - 1
        Unsch   - 28
So, why isn't the count showing 57 instead?
It seems to only be counting the ones that have Status=Patch Available
and ignoring those with Patch Info=Patch Available.


-Donald

Hernan Cunico wrote:
> Howdy,
> it may sound weird asking this now but I'm either creating JIRAs the
> wrong way or we are not displaying the all the info in
> http://issues.apache.org/jira/browse/geronimo (or I just don't know how
> to read it)
>
> On the JIRA front page for GERONIMO you can see open issues due to be
> fixed per version.
> When I create a JIRA for a specific version I normally specify the
> "affected version" (let's say 2.0-M2) in the *Affects Version/s:* box
> and leave the *Fix Version/s:* empty as I don't really know for sure
> when that issue is going to be fixed unless I am the assignee.
>
> This issue I just created does not get listed (counted actually) for
> that particular version in the project's JIRA home page.
>
> Is this query is automatically provided by JIRA or we can customize it
> to show the affected version instead?
> At this particular point in time the actual setting show 5 open issues,
> if we could change it to affected versions it would show 16.
>
> Does this make any sense at all?
>
> Again, it might be just me not really understanding how to use JIRAs.
>
> Comments appreciated
>
> Cheers!
> Hernan
>
>
>



------=_Part_227825_6323496.1169907185970--