Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 43884 invoked from network); 12 Jun 2006 23:19:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Jun 2006 23:19:27 -0000 Received: (qmail 55958 invoked by uid 500); 12 Jun 2006 23:19:16 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 55792 invoked by uid 500); 12 Jun 2006 23:19:15 -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 55474 invoked by uid 99); 12 Jun 2006 23:19:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jun 2006 16:19:13 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=MSGID_FROM_MTA_HEADER,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [203.121.192.7] (HELO mail.e-wire.net.au) (203.121.192.7) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jun 2006 16:19:12 -0700 Received: from developer (mail.e-wire.net.au [127.0.0.1]) by mail.e-wire.net.au (8.13.1/8.13.1) with ESMTP id k5CNENgD013046 for ; Tue, 13 Jun 2006 07:14:24 +0800 Message-Id: <200606122314.k5CNENgD013046@mail.e-wire.net.au> Received: from 203-121-204-130.e-wire.net.au [203.121.204.130] for mail.e-wire.net.au (EHLO developer) via SMTP; Tue, 13 Jun 2006 07:14:25 +0800 Reply-To: From: "Gav...." To: Subject: RE: [jira] Subscription: FOR-open-with-patch Date: Tue, 13 Jun 2006 07:18:43 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <448D5950.7080906@apache.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcaOGG3ZpBlhcMedTSey29SyuL1GIQAXgmAg X-BitDefender-SpamStamp: 1.1.4 049000040111ABAAAAEAAAAAAAAAAABAAAAAAAAAAAAAQ X-BitDefender-Spam: No (0) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Neil Applebaum replies :- Does your admin have access to run a SQL Query on your database? Just run "select * from jira.filtersubscription" and you'll see the owner of the filter (as the username) - Neal - HTH Gav... > -----Original Message----- > From: Ross Gardler [mailto:rgardler@apache.org] > Sent: Monday, 12 June 2006 8:09 PM > To: dev@forrest.apache.org > Subject: Re: [jira] Subscription: FOR-open-with-patch > > Gav.... wrote: > > > >>-----Original Message----- > >>From: Ross Gardler [mailto:rgardler@apache.org] > >>Sent: Monday, 12 June 2006 4:11 PM > >>To: dev@forrest.apache.org > >>Subject: Re: [jira] Subscription: FOR-open-with-patch > >> > >>Gav.... wrote: > >> > >>>>-----Original Message----- > >>>>From: Ross Gardler [mailto:rgardler@apache.org] > >>>>Sent: Monday, 12 June 2006 6:02 AM > >>>>To: dev@forrest.apache.org > >>>>Subject: Re: [jira] Subscription: FOR-open-with-patch > >>>> > >>>>jira@apache.org wrote: > >>>> > >>>> > >>>>>Issue Subscription > >>>>>Filter: FOR-open-with-patch (12 issues) > >>>>>Subscriber: rgardler > >>>> > >>>>We still seem to have two incompatible messages from JIRA. Both appear > >>>>to be set up by myself (i.e. Subscriber: rgardler). > >>>> > >>>>Some time ago, before the existence of the "patch" field, I created a > >>>>filter that may well have had the same name. This filter would create > >>>>different results as it worked by assuming an attachment was a patch. > I > >>>>also tried to set up a mail subscription, but this never seemed to > work. > >>>> > >>>>I checked this last week at Davids request and saw no second filter > >>>>called "FOR-open-with-patch", I see only one filter with a single > >>>>subscription. I also only see one FOR-* filter with a subscription, > the > >>>>correct one (i.e. returns 7 issues) See [1] > >>>> > >>>>Does anyone have any idea how this is happening? If I it dead silence > >>>>here I'll go to the infra@ list. Can I please request that everyone at > >>>>least looks at the filters in Jira and ensure that you can't see what > is > >>>>causing this double subscription, that way I can tell infra we have > done > >>>>what checks we can. > >>>> > >>>>Ross > >>>> > >>>>[1] http://issues.apache.org/jira/secure/ManageFilters.jspa > >>> > >>> > >>>I don't know why it is happening, but to confirm from the above link > for > >> > >>me > >> > >>>I can see only one instance of FOR-open-with-patch - created by David > >>>Crossley. > >>> > >>>Everyones view of this page will show differently for the 'Your > Filters' > >>>section, i.e. - filters created by you. > > ... > > > Under 'Manage > > Filters' I have a section called 'Your Filters' and under that one > called > > 'Viewable Filters' . > > I see it now - thanks. Nothing in there indicating the rogue filter > exists. > > > Also, having a section called 'Viewable Filters' makes me think there > must > > also be a section somewhere where 'Hidden Filters' may exist. And our > > duplicate may live there. > > I think "viewable filters" are ones you have the privs to view, i.e. you > are a member of the project. Since I'm an admin I should be able to see > all the filters, but can only see the one FOR-open-with-patch created by > David. > > We'll have to see if your email to the Jira Users list comes up with > anything. > > Ross > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006