You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Joe Bohn <jo...@earthlink.net> on 2005/11/01 23:04:16 UTC
How to identify a JIRA with a patch.
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?
Joe
Re: How to identify a JIRA with a patch.
Posted by Dain Sundstrom <da...@iq80.com>.
Registered JIRA users already have permission to edit issues, so this
should not be a problem.
-dain
On Nov 1, 2005, at 2:53 PM, Dain Sundstrom wrote:
> Done.
>
> Geronimo and Geronimo-dev issues now have a custom "Patch" field at
> the bottom of the issue. Here is a report:
>
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?
> mode=hide&requestId=12310367
>
> Now I'll try to figure out the security issue raised by brett.
>
> -dain
>
>
> On Nov 1, 2005, at 2:37 PM, Joe Bohn wrote:
>
>
>>
>> I like this suggestion for when you only want to pull up a list of
>> JIRAs that have patches attached (very creative).
>>
>> One of the other things I was hoping to use this for was to look
>> at a release, component, whatever .... and see how many potential
>> fixes we already had and how many are still "untouched". It would
>> also be a good way for non-committers to see what items are open
>> and waiting for attention. We could do the inverse of the "patch"
>> search but it would be nice to see both types in one view with
>> some differentiation.
>>
>> Joe
>>
>>
>> Brett Porter wrote:
>>
>>
>>> Not as far as I know. I'm tracking a JIRA ticket at Atlassian for
>>> the
>>> ability to detect the existence of an attachment, but that stiff
>>> doen't designate if its a patch unfortunately.
>>> In our project we just query for "patch" in any of the text
>>> fields. We
>>> generally find that people type that somewhere when attaching it.
>>> - Brett
>>> On 11/2/05, Joe Bohn <jo...@earthlink.net> 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?
>>>>
>>>> Joe
>>>>
>>>>
>>
>
Re: How to identify a JIRA with a patch.
Posted by Dain Sundstrom <da...@iq80.com>.
Done.
Geronimo and Geronimo-dev issues now have a custom "Patch" field at
the bottom of the issue. Here is a report:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?
mode=hide&requestId=12310367
Now I'll try to figure out the security issue raised by brett.
-dain
On Nov 1, 2005, at 2:37 PM, Joe Bohn wrote:
>
> I like this suggestion for when you only want to pull up a list of
> JIRAs that have patches attached (very creative).
>
> One of the other things I was hoping to use this for was to look at
> a release, component, whatever .... and see how many potential
> fixes we already had and how many are still "untouched". It would
> also be a good way for non-committers to see what items are open
> and waiting for attention. We could do the inverse of the "patch"
> search but it would be nice to see both types in one view with some
> differentiation.
>
> Joe
>
>
> Brett Porter wrote:
>
>> Not as far as I know. I'm tracking a JIRA ticket at Atlassian for the
>> ability to detect the existence of an attachment, but that stiff
>> doen't designate if its a patch unfortunately.
>> In our project we just query for "patch" in any of the text
>> fields. We
>> generally find that people type that somewhere when attaching it.
>> - Brett
>> On 11/2/05, Joe Bohn <jo...@earthlink.net> 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?
>>>
>>> Joe
>>>
>
Re: How to identify a JIRA with a patch.
Posted by Joe Bohn <jo...@earthlink.net>.
I like this suggestion for when you only want to pull up a list of JIRAs
that have patches attached (very creative).
One of the other things I was hoping to use this for was to look at a
release, component, whatever .... and see how many potential fixes we
already had and how many are still "untouched". It would also be a good
way for non-committers to see what items are open and waiting for
attention. We could do the inverse of the "patch" search but it would be
nice to see both types in one view with some differentiation.
Joe
Brett Porter wrote:
> Not as far as I know. I'm tracking a JIRA ticket at Atlassian for the
> ability to detect the existence of an attachment, but that stiff
> doen't designate if its a patch unfortunately.
>
> In our project we just query for "patch" in any of the text fields. We
> generally find that people type that somewhere when attaching it.
>
> - Brett
>
> On 11/2/05, Joe Bohn <jo...@earthlink.net> 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?
>>
>>Joe
>>
>
>
>
Re: How to identify a JIRA with a patch.
Posted by Brett Porter <br...@gmail.com>.
Not as far as I know. I'm tracking a JIRA ticket at Atlassian for the
ability to detect the existence of an attachment, but that stiff
doen't designate if its a patch unfortunately.
In our project we just query for "patch" in any of the text fields. We
generally find that people type that somewhere when attaching it.
- Brett
On 11/2/05, Joe Bohn <jo...@earthlink.net> 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?
>
> Joe
>
Re: How to identify a JIRA with a patch.
Posted by Joe Bohn <jo...@earthlink.net>.
David Blevins 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
>
>
It would be awesome if we could get a custom field. Would this be
something that we would have to work with the infrastructure folks to
get implemented?
Can we agree upon a poor man's version in the meantime by altering the
title or something else that we could see plainly in the reports?
Joe
Re: How to identify a JIRA with a patch.
Posted by Brett Porter <br...@gmail.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 <da...@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
>
Re: How to identify a JIRA with a patch.
Posted by David Blevins <da...@visi.com>.
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