Hi Sean,
are you sure? It looks like just a anonymous user triggers this, see
http://issues.apache.org/jira/browse/TOBAGO-54?page=all
Regards,
Volker
Sean Schofield wrote:
Done. Users must have the same permissions as for Create Issue (which
is to say they must be logged in.)
Sean
Sorry, I got mixed up while fixing the workflow. There are two
separate concepts: 1.) workflow, 2.) workflow scheme. I had only
changed the scheme but it was pointing to the wrong workflow. It
should be fixed now.
Sean
On 4/13/06, Volker Weber [EMAIL PROTECTED] wrote:
Hi Sean,
are you
On 4/13/06, Sean Schofield [EMAIL PROTECTED] wrote:
Sorry, I got mixed up while fixing the workflow. There are two
separate concepts: 1.) workflow, 2.) workflow scheme. I had only
changed the scheme but it was pointing to the wrong workflow. It
should be fixed now.
I'm able to cancel
On 4/12/06, Sean Schofield [EMAIL PROTECTED] wrote:
Was there ever a cancel patch option? My guess is no. But I can try
to add one ;-)
On 2/27/06, Sean Schofield [EMAIL PROTECTED] wrote:
I added
a Cancel Patch operation. For now it just dumps you to Open even
if the status beforehand
Hmmm. When I went to add it I noticed that the state is part of the
Derby workflow. They probably took it out ;-) Lemme see if we can
add our own.
Sean
On 4/12/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 4/12/06, Sean Schofield [EMAIL PROTECTED] wrote:
Was there ever a cancel patch
Hey Sean,
I went to go fix issue TOMAHAWK-210 one last time, but now there's no
Cancel Patch option available for any issues with a patch.
Provide Patch still shows up, though. I'm logged in and can even
edit issues.
On 4/8/06, Anonymous (JIRA) dev@myfaces.apache.org wrote:
[
Done. Users must have the same permissions as for Create Issue (which
is to say they must be logged in.)
Sean
On 3/21/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
I'm wondering if it'd be possible to restrict Provide Patch to
logged-in users.
It's annoying when an anonymous user triggers
Is there any way to have the JIRA notification mail state when one of
these buttons was pushed?
Right now we only get the following (Anon said there was a patch; I
cancelled the process because there wasn't one).
Anonymous (JIRA)
[
I'm wondering if it'd be possible to restrict Provide Patch to
logged-in users.
It's annoying when an anonymous user triggers this with a patch
because there's no way to identify them in order to educate them as to
why it was the wrong thing to do.
On 3/21/06, Mike Kienenberger [EMAIL PROTECTED]
