Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 17036 invoked from network); 16 Jan 2006 10:58:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Jan 2006 10:58:33 -0000 Received: (qmail 35801 invoked by uid 500); 16 Jan 2006 10:58:32 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 35588 invoked by uid 500); 16 Jan 2006 10:58:31 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 35577 invoked by uid 99); 16 Jan 2006 10:58:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2006 02:58:31 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [212.23.3.142] (HELO rutherford.zen.co.uk) (212.23.3.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2006 02:58:30 -0800 Received: from [82.69.78.226] (helo=[192.168.0.2]) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1EyS3t-0001Ld-Jp for dev@forrest.apache.org; Mon, 16 Jan 2006 10:58:09 +0000 Message-ID: <43CB7C37.2050707@apache.org> Date: Mon, 16 Jan 2006 10:57:59 +0000 From: Ross Gardler User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: [FOR Filters] Question ? References: <43CB7141.5070003@pcotech.fr> In-Reply-To: <43CB7141.5070003@pcotech.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-Rutherford-IP: [82.69.78.226] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Cyriaque Dupoirieux wrote: > Hi, > > I wonder why theFOR-urgency-blocker filter of JIRA only returns one > FOR and not 6 (There are 6 blockers FOR in the JIRA portal) 5 of those "blockers" are on plugins not core. The FOR-urgency-blocker filter is showing us blockers for core, i.e. blockers on our next release - plugins have a separate release cycle and so are not bolckers to core. See earlier discussions for more. Ross