Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 68219 invoked from network); 30 Jun 2006 22:53:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Jun 2006 22:53:39 -0000 Received: (qmail 87989 invoked by uid 500); 30 Jun 2006 22:53:39 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 87763 invoked by uid 500); 30 Jun 2006 22:53:38 -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 87754 invoked by uid 99); 30 Jun 2006 22:53:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jun 2006 15:53:38 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of mcintyre.a@gmail.com designates 66.249.92.172 as permitted sender) Received: from [66.249.92.172] (HELO ug-out-1314.google.com) (66.249.92.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jun 2006 15:53:37 -0700 Received: by ug-out-1314.google.com with SMTP id m3so1029229uge for ; Fri, 30 Jun 2006 15:53:16 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ei8/0SEaBcD9QY97EcCxF7KlhgNaFup0gelt4ExyGROYjcyxj/jrYDGIc/a0wCekZ/wrSISRG/Up6+MV4sS+AdCwdP39WpZ5DbZiatPbTeU9pGQoHwM9HDYY6t0XS8qcn8+ZCIvgwvJhdZq+rytp4u7Rnh6wl7UL4BF/tnufSpE= Received: by 10.67.26.7 with SMTP id d7mr3519080ugj; Fri, 30 Jun 2006 15:53:16 -0700 (PDT) Received: by 10.67.27.4 with HTTP; Fri, 30 Jun 2006 15:53:16 -0700 (PDT) Message-ID: <54ac72d70606301553j4569c032kcc5a089120885b33@mail.gmail.com> Date: Fri, 30 Jun 2006 15:53:16 -0700 From: "Andrew McIntyre" To: derby-dev@db.apache.org Subject: Re: making a jira filter public In-Reply-To: <44A5AA70.4090007@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44A5AA70.4090007@sun.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 6/30/06, Rick Hillegas wrote: > The 10.2 release page contains a link to a JIRA filter I created. How do > I make this filter public? Right now, other people are getting a > permissions problem when they click on the link. When you click Find Issues in the main JIRA menubar, there is a Filters: Manage link in the top left under the menubar. On the Manage filters page, you can choose to share any of your saved filters either globally or just with a specific group (e.g. just with derby-developers) andrew