If the user enters multiple bugs, separated by commas, does each become it's
own link? Or is the client just doing a straight replace of %BUGID%?
Also, while it might be trivial to add a property to *force* entering a bug
id, I think it's a bad idea, because required fields always end up making
life harder for the end users, not every checkin is associated with a bug
necessarily and also because you can't require users to use the GUI tool
(they could always drop down to svn command line). So getting developers to
always put in bug numbers for checkins is a social problem, not a technology
From: Mark Phippard [mailto:MarkP@softlanding.com]
Sent: Saturday, August 21, 2004 1:20 PM
Cc: firstname.lastname@example.org; MarkP@softlanding.com; email@example.com
Subject: Re: [TSVN] Re: Integration with bug tracking tools
I am in a WebMail client, so forgive me if this doesn't format well.
>> 6) My Bug ID's can sometimes have embedded blanks. Will that be OK
>> in your system? For example might be XYZ 0001.
>Yes, sure. Just set the property
>bugtraq:number to "false" - then any text is valid.
My concern was that it might mess up your log parsing routine. I am not
clear how you accurately extract the Bug ID from the log message, that is
also why I thought a specific property would be helpful.
Also, the URL might have a problem if the space is not encoded to %20,
although I imagine that most systems would auto-escape it for you.
My bug system has letters and numbers, so the number property is of no
value. How about a property to require any value, meaning it cannot be left
blank? Or is that already implied by the presence of the properties that
turn the feature on?
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Aug 21 21:36:05 2004