Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 93759 invoked from network); 12 Jun 2006 11:38:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Jun 2006 11:38:42 -0000 Received: (qmail 97790 invoked by uid 500); 12 Jun 2006 11:38:42 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 97615 invoked by uid 500); 12 Jun 2006 11:38:41 -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 97604 invoked by uid 99); 12 Jun 2006 11:38:41 -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 04:38:41 -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 04:38:39 -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 k5CBXoNg016598 for ; Mon, 12 Jun 2006 19:33:51 +0800 Message-Id: <200606121133.k5CBXoNg016598@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; Mon, 12 Jun 2006 19:33:51 +0800 Reply-To: From: "Gav...." To: Subject: RE: [jira] Subscription: FOR-open-with-patch Date: Mon, 12 Jun 2006 19:38:10 +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: <448D21B0.2070101@apache.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 thread-index: AcaN90RcuEqPJ/XaQdy/qXlS2RDqsAAHBu0w X-BitDefender-SpamStamp: 1.1.4 049000040111ABAAAAEAAAAAAAAAAABAAAAAAAAAAAAAQAAAI 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 > -----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. What does yours say. > > I can't see a "Your Filters" link, where is it? I only see a "Manage > Filters" (perhaps because I am an admin?) Possibly, or because you have not set up any specific filters for you - I have set one up and so I presume if I delete it the section will disappear - - er, just done that, nope the section is still there. Under 'Manage Filters' I have a section called 'Your Filters' and under that one called 'Viewable Filters' . So it could be that because you are Admin you have no need for such a section (don't see why not though!) 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 am guessing, I am no expert in the Admin of Jira, I did download it for evaluation but could not afford the licence, so bought something cheaper for my purposes instead. > > > There have been Issues with Jira in the past where filters can get > hidden > > but remain active if the creator of the filter is deleted, and other > such > > bugs.[1][2] > > Ahhh... We my be hitting such a bug then. > > > I am subscribed to the jira-users list, I'll do a search and see if > anything > > like it comes up, otherwise I'll email the problem to them and see what > they > > say. > > That would be great - thanks. I have emailed jira-users and will forward on the reply. > > > I take it infra@ manage jira then do they? > > Yes, the infra@ list is where all things pertaining to ASF > infrastructure are handled. Ok, cool. Gav... > > Ross > > > [1] - http://jira.atlassian.com/browse/JRA-8059 > > [2] - http://jira.atlassian.com/browse/JRA-6561 > > > -- > 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