Opened 20 years ago
Last modified 13 years ago
#508 new enhancement
'Related checkins' feature — at Initial Version
| Reported by: | dobes | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | unscheduled |
| Component: | ticket system | Version: | 0.7 |
| Severity: | normal | Keywords: | xref |
| Cc: | gary.wilson@…, chris-r@…, kevin@…, braden@…, mikko.rantalainen@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
In CVSTrac, a ticket has a field called "Related Checkins" which shows a list of checkins (they would be changsets in trac) and their comments.
You can add and remove from this list by editing a comma-seperated list of related checkins.
However, the most useful part, is that by putting a ticket number into your checkin message, it automatically adds that checkin to the "Related Checkins" of the ticket.
Eg. svn commit -m 'Added the ability to edit existing tickets. This fixes ticket #411'
Then when you view the ticket #411 you can see that checkin there without doing any more work.
This feature made CVSTrac sooo useful, because it was very easy to make this connection from the ticket to the checkins that attempted to fix it.
bonus marks:
The whole idea of two-way linking useful in general — once you had this feature you might also show wiki pages linking to a ticket, or tickets linking to a wiki page. Often with information given by people, the incoming links are as relevant as the outgoing ones.
BUT the automatic pingback from the checkins to the tickets is by far the most useful!
