McKenna, Simon (RGH) wrote:
> Hello again
> (is the rest of the world is sick of Australiens yet?;-)
No. Why? Were you guys bad?
> Was just playing with the new Bug-ID/Issue-Nr option in the
> commit dialog, and thinking about how our team can use this.
>
> We use devhound for bug/issue tracking, etc, and each issue
> has an ID assigned to it, so we can link them to revisions.
>
> I like the way TortoiseSVN adds the text to the log message,
> but it would be nice to allow text other than "Bug-ID:" to be used,
> simply because it may not be a bug that was in the revision.
Just add the registry key
HKCU\Software\TortoiseSVN\BugIDFormat
to what you want that string to be. The default value used in TSVN right
now is:
"Bug-ID : %BUGID%"
As you can see, the part "%BUGID%" is replaced with the issue number
text entered in the commit dialog.
> So perhaps in the Settings, when a user has the "Show Bug-ID"
> checkbox ticked, an edit box is enabled allowing them to set the
> text to be prefixed (you could of course default to "Bug-ID").
>
> For our team it would be "Issue-ID"
>
> You could then show this user-defined value in commit dialog
> instead of generic Bug-ID/Issue-Nr text.
The problem with this approach is that it's machine dependent, not
project dependent. For that to work, we would need a config file in the
repository which each client could then use. That way you could specify
that string in the server config file and TSVN would then use the right
string for each project (which might have very different bug trackers
assigned to them).
> The ability to open a URL inside the log window(s) would also be
> nice. For example, instead of adding a Bug-ID, our team could
> paste a URL providing a direct link between systems. This could
> then be available for linking when viewing log messages in Tortoise,
> or another SVN tool (eg. the RSS newsfeed in WebSVN)
I've discussed this with Michael Pryor from FogCreek Software (hey, they
sent me two music CD's from my wishlist!) before. In fact, the whole
idea for the bug-id field in the commit dialog was his request. And also
the ability to open a bugtracking URL which TSVN would put together from
project/file related data. But again, we would need a server config file
for this. That's why issue 1974 was opened in the Subversion issue
tracker. See my and Michaels comments on that issue there.
Maybe you can also add your comments there so that the issue doesn't get
forgotten.
> Am happy to file an issue for this if the hive mind agrees.
I was just thinking if Subversion doesn't implement that config file on
the server, maybe we could just define our own. If we define that a file
with the name:
SVNProjectConfig
is used by TSVN (and maybe other clients which want to use it) then we
would have such a config file. It wouldn't be part of the Subversion API
or standard, but if they don't want that....
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Aug 17 19:29:49 2004