Ticket #1495 (closed defect: duplicate)
Opened 7 years ago
Last modified 6 years ago
Changesets Associated with this Ticket
| Reported by: | root@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | ticket system | Version: | 0.8.1 |
| Severity: | normal | Keywords: | tickets checkins commits tracking |
| Cc: | enigma@… | ||
| Release Notes: | |||
| API Changes: | |||
Description
Trac needs to be able to scan svn commit messages and build a list of changesets that mention that ticket number. That is currently the only feature missing from Trac that I miss from using CVSTrac.
For example, if I have a set of commits with these messages:
- "ticket:45 and ticket:80 are both fixed with this commit - change x to y and it works now"
- "ticket:12"
- "ticket:34 - I've just fixed this really annoying problem!"
Should result in the following:
Ticket 45
(description with someone whining about a problem like me :)
Related Commits / Changesets
- changeset:X :: "ticket:45 and ticket:80 are both fixed with this commit - change x to y and it works now"
Ticket 80
(description)
Related Commits / Changesets
- changeset:X :: "ticket:45 and ticket:80 are both fixed with this commit - change x to y and it works now"
Ticket 12
(description)
Related Commits / Changesets
- changeset:X :: "ticket:12"
Ticket 34
(description)
Related Commits / Changesets
- changeset:X :: "ticket:34 - I've just fixed this really annoying problem!"
TRAC RULES'''
Attachments
Change History
comment:1 Changed 7 years ago by cboos
- Resolution set to duplicate
- Status changed from new to closed
comment:2 Changed 7 years ago by mgood
Also, take a look at the SVN post-commit script. This script is currently shipped with Trac and will automatically add comments to tickets and can even close tickets based on the context where you mention the ticket number. Most of the documentation is provided in comments at the top of that file.
comment:3 Changed 7 years ago by mgood
- Milestone 0.9 deleted



Well, that's what will be provided by TracCrossReferences.
If you are impatient/curious, you can have a try
of the source:branches/cboos-dev/xref-branch
and give us some feedback!
For the record, initial request for this particular aspect of cross-references was done in #508.