Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 07F6FC965 for ; Wed, 27 Jun 2012 08:39:25 +0000 (UTC) Received: (qmail 44960 invoked by uid 500); 27 Jun 2012 08:39:24 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 44772 invoked by uid 500); 27 Jun 2012 08:39:24 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 44754 invoked by uid 99); 27 Jun 2012 08:39:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2012 08:39:23 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [80.12.242.42] (HELO smtpout.wanadoo.co.uk) (80.12.242.42) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2012 08:39:14 +0000 Received: from mail.homeinbox.net ([2.24.223.107]) by mwinf5d30 with ME id TLeu1j0072KedSS03LeuyD; Wed, 27 Jun 2012 10:38:54 +0200 Received: from localhost (localhost [127.0.0.1]) by mail.homeinbox.net (Postfix) with ESMTP id 151D0EAB68C for ; Wed, 27 Jun 2012 09:38:54 +0100 (BST) X-Virus-Scanned: Debian amavisd-new at homeinbox.net Received: from mail.homeinbox.net ([127.0.0.1]) by localhost (mail.homeinbox.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmtESppc8wPY for ; Wed, 27 Jun 2012 09:38:46 +0100 (BST) Received: from [192.168.23.9] (study03.dev.local [192.168.23.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.homeinbox.net (Postfix) with ESMTPSA id 601C4EAB688 for ; Wed, 27 Jun 2012 09:38:46 +0100 (BST) Message-ID: <4FEAC68E.30200@apache.org> Date: Wed, 27 Jun 2012 09:38:38 +0100 From: Mark Thomas User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Commons Developers List Subject: Re: JIRA Administration References: <4FEAC44E.4090102@apache.org> <4FEAC5D8.5030300@free.fr> In-Reply-To: <4FEAC5D8.5030300@free.fr> X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 27/06/2012 09:35, Luc Maisonobe wrote: > Le 27/06/2012 10:29, Mark Thomas a écrit : >> On 27/06/2012 09:21, Jörg Schaible wrote: >>> Hi, >>> >>> does anybody know, what is required to administer a JIRA project? >> >> You need an existing admin to grant you the admin role. > > Hi Mark, > > Some recent issues for Imaging have been assigned to me, despite I do > not work (at least yet) to this component. I wrongly assumed the > reporter did assign them as I am listed as project leader, but this > assumption was wrong. > > Looking at the administration apge for the 48 projects for which I am > somehow identified as lead, I noticed that both Imaging and OGNL have a > default assignee to "project lead" while the other one have "unassigned" > by default. > > I cannot change this myself. Really? As a project admin that surprises me. Oh well. > Could someone with Jira administration set these two projects to > "unassigned" by default too ? Done. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org