Katana,
thanks for your info.
Since this is a bit off-topic for TSVN (except for my last comment -
Stefan, can you comment on that?) I'd suggest moving over to the trac
list (assuming you're monitoring that as well?).
Katana wrote:
> thanks to the wiki syntax, it can be easily achieved.
> [...]
> Even funnier, Trac comes with a post commit hook that let you modify
> your tickets using a simple syntax in the commit messages:
> "Updated foo.xx, fixes #XX and references #YY" will add the message as
> a comment on tickets XX and YY, close XX and leave YY opened. In the
> tickets, a link on #XX / YY will let you go to the changeset, and in
> the commit message on the changeset, you will get links to the ticket.
Somehow I must have missed that or made it non-funct accidentally - or
is this a post-0.7.1 feature?
While I see this is actually working e.g. on Trac's ticket #841, I still
have to read through the comments to find the changeset links. Still
valuable though.
What I'd prefer would be a single 'Changesets' link in the ticket view
which would take me to a list of tickets similar to the reports already
available. Partly I achieved that by defining a report (no. 9) with the
following SQL and link in the ticket view:
<a href="/trac/cgi-bin/trac.cgi/report/9?TICKET=3">Changesets</a>
-- ## 9: Changesets for Ticket ## --
-- * All changesets for ticket.
-- * Prerequisite: commit log messages contain 're #<n>' where
-- n is the ticket number.
-- Must be called with the ticket nr as argument, like this:
-- http://projects.edgewall.com/trac/reports/9?TICKET=123
select rev as Changeset, time, author, message
from revision where message like '%re #$TICKET'
This gives me the desired report but I found no way to have the
changeset numbers appear as links to the changeset view :-( Plus the
report shouldn't appear in the report list since it's not supposed to be
called directly from there.
> basically, nothing links a ticket resolution to a changeset.
Technically true and I'd prefer having that link in a separate table -
but I can live with the implicit link in the comment, since it's ensured
by the pre-commit hook anyway.
> And of course, on the changeset view, you have a list of added /
> modified / deleted files, as well as the diff and a link to the
> unified diff.
Yep, I knew that, just missed the link from a ticket to the changeset(s).
> As I said before, nice and simple :)
Absolutely true - the only thing missing would be a combobox in TSVNs
commit dialog with the available open tickets in Trac. I would think
something like this would be needed for any bug tracking system and
could be implemented generically. I would imagine a new bugtraq property
in which I could specify a script/program/... which would deliver the
appropriate ticket numbers. If this property was set, TSVN could call it
and fill the above-mentioned combobox with these values.
Just some thoughts...
Lars.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 27 16:17:40 2004