On 7/25/06, Hubert Rabago <[EMAIL PROTECTED]> wrote:
Thanks. Looks like it's working:
https://issues.apache.org/struts/browse/STR-2917
Great! See, if I leave things on my TODO list long enough, they fix
themselves. :) I think Jeff upgraded JIRA recently, that probably did
it.
--
Wendy
---
On 7/25/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
If you refer to the issue number in the commit message, it should show
up on the 'Subversion Commits' tab on the issue after a little while.
I don't think that's working right now, though. We probably need to
open a ticket with infrastructure to
On 7/25/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 7/25/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> After the fact, just add a comment with the ViewVC URL to the commit.
Bad job of editing. Trying again: If you commit without mentioning
the issue number in the commit message, then just ad
On 7/25/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
After the fact, just add a comment with the ViewVC URL to the commit.
Bad job of editing. Trying again: If you commit without mentioning
the issue number in the commit message, then just add a comment to the
issue with the revision number.
On 7/25/06, Hubert Rabago <[EMAIL PROTECTED]> wrote:
The last time I fixed a bug, we were still using Bugzilla. Anything I
need to know before marking a Jira ticket as fixed? For instance, how
do they get linked to an svn commit? Is it in the commit message?
If you refer to the issue number
The last time I fixed a bug, we were still using Bugzilla. Anything I
need to know before marking a Jira ticket as fixed? For instance, how
do they get linked to an svn commit? Is it in the commit message?
Hubert
-
To unsubsc
