[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Feature request: beeter issue tracker integration in history dialog

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sat, 01 Jun 2013 18:26:50 +0200

On 01.06.2013 18:03, Friedrich Brunzema wrote:
>
> >Ahem:
> >* Show log for the TSVN working copy root.
> >* browse to revision 24233
> >* hover the mouse pointer over the blue, underlined '477'
> >* notice the tooltip
> >* click
>
> >Stefan
>
> Wow, that was a quick implementation and pre-deployment on my system!
> RTFM, Friedrich!. You have me intrigued - how does the system know that
> "477" is an issue? What did you have to do in your commit comment to
> identify the issue? Does it look at "issue #"? What if I have
> "ABC-8788" as reference to my issue tracker, would it still work? How
> does it get the URL? Go to the source, Luke? (or will you just tell me?)

right-click on a folder in the TSVN wc, click on "properties".
In the properties dialog, double click on one of the bugtraq: properties
to open the config dialog for those.

The first item you see is the url to access the issue tracker.
below the middle are the regexes to extract the issue number from the
log message: the first part matches "Fixes issue #XXX" for example, and
the second one then extracts the issue number that's needed for the url,
in our case the digits only.

http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3056857
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-06-01 18:26:58 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.