Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of brett.porter@gmail.com
 designates 66.249.82.205 as permitted sender)
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=SIoVcs8UMlq7C1o31UPTF0DgXugOfF/cENT2WzG2s2YjMM0hUpk5e20gGUnuWrEBI2jg/8x5e4qpxvKpAgGyVkrnLycCkfhDpAXQQJnlfcZfOB92g2jYzI1aB8JKQO2o1/w3ZHwT3gC4665hy9bQUDivTw7a7ZbPTGBNYpbDZi8=
Message-ID: <9e3862d80511011427k5129069fv21429453a5a98fc8@mail.gmail.com>
Date: Wed, 2 Nov 2005 09:27:17 +1100
From: Brett Porter <brett.porter@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: How to identify a JIRA with a patch.
In-Reply-To: <E07D648E-A50E-411A-B9CC-D6182670E71F@visi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4367E660.6090300@earthlink.net>
	 <E07D648E-A50E-411A-B9CC-D6182670E71F@visi.com>

The problem with this is that when a person later attaches a file,
they usually don't have permissions to edit the issue and adjust the
custom field, so it only works when the attachment comes with
creation.

Maybe this is something that could be added to the ASF customisations
though (the bit that makes them approve it is ASL'd) - maybe you could
propose this on infrastructure@ - Jeff Turner will likely be able to
offer an opinion.

- Brett

On 11/2/05, David Blevins <david.blevins@visi.com> wrote:
> On Nov 1, 2005, at 2:04 PM, Joe Bohn wrote:
>
> > Is there any way to get a view of JIRAs that have files(patches)
> > attached?
> >
> > If not, can we begin some kind of convention?  I noticed that some
> > folks have added (Patch) to the start of the title for a few
> > JIRAs.  Do you think that would be helpful?
> >
> > I image it must be a pain for the committers to get a view of the
> > available patches.
> >
> > Any other suggestions?  Anybody how other projects manage this?
> >
>
> This just occurred to me, but I wonder if we couldn't add a "patch"
> custom field, which would be even better than knowing which jira
> items have files attached (as that's not even possible anyway).
>
> Assuming everyone used it, it would be really easy to find and report
> them then.
>
> Not exactly sure how custom fields work in JIRA, but I just noticed
> it glancing through the docs just now (http://www.atlassian.com/
> software/jira/docs/v3.3.2/customfields/overview.html)
>
> -David
>