#1495 closed defect (duplicate)
Changesets Associated with this Ticket
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | ticket system | Version: | 0.8.1 |
Severity: | normal | Keywords: | tickets checkins commits tracking |
Cc: | enigma@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal 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 (0)
Change History (3)
comment:1 by , 20 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:2 by , 20 years ago
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 by , 19 years ago
Milestone: | 0.9 |
---|
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.