1. See which files were changed in order to fix a given ticket?
As long as you do not use a pre-/post- commit hook script, Trac will not tie a ticket to a set of file (or a set of file to a ticket). Checkout the script in the contrib/ directory of Trac distribution. The idea behind these scripts is to describe each commit with a keyword (such as "closes" or "fixes") and a ticket number. The pre-/post- commit hook script then update the Trac DB so that the commited files are tied with the specified ticket, and the ticket status is updated accordingly.
2. Create a ticket report that lists the tickets addressed between any 2 revisions (or changesets)?
I don't think there's a direct easy way to do this, as changesets (or revisions) are defined globally for a repository, whereas a ticket usually targets a specific branch in the repository.
And one last thing: I thought that Subversion updated the entire repository's revision number when a change was made,
That is true.
Trac appears to diplay the revision on a per-file basis.
Trac uses two idioms: a "changeset" defines the set of files changed in a Subversion revision, while a "revision" is used to track a single file of a defined changeset.
It's correct, of course, but is there any way to see the global revision number?
This is called a "changeset" in Trac. If you walk in the repository "Browser", each row shows a single file, with a revision number, and a changeset number. If you click on the changeset link, you'll get the whole set of files that have been changed alltogether in a Subversion revision.
Changesets are great, but I can only see the changeset number, not the Svn revision number.
Those numbers are the same ;-) Cheers, Manu _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
