Backlinks for tickets in comment history

Description

Summary

Enables intra-Trac references between tickets. When a comment on ticket A references ticket B, a comment is made on ticket B letting you know that ticket A has referenced it.

See also: TicketBackLinksMacro

More detail

TracBacksPlugin provides internal trackback functionality between tickets in a Trac instance.

Scenario: If developer A is working on ticket 1 and developer B is working on ticket 2 and writes some notes (on ticket 2) how it’s related to ticket 1, it automatically makes a (ticket-2)-to-(ticket 1) link that’s easy to follow to get more details. So far so good. However, developer A has no idea her ticket has just been discussed on ticket 2, and tinkers on blithely unaware of what is going on around her, because there is no reciprocal (ticket 1)-to-(ticket 2) link.

How can we automatically indicate that tickets are being discussed at other tickets? TracBacks. What this plugin does is simply to create that reciprocal (ticket 1)-to-(ticket 2) link so that anyone looking at ticket 1 can see it has been talked about on ticket 2 as well.

Bugs/Feature Requests

Existing bugs and feature requests for TracBacksPlugin are here. If you have any issues, create a new ticket.

Download and Source

Download the zipped source, check out using Subversion, or browse the source with Trac.

Example

Note: This plugin will not retroactively create trackbacks for existing comments.

Adding the following comment in ticket A

Results in the following tracback in ticket B

Recent Changes

[5618] by k0s on 04/27/09 23:20:55

handle case where the comment/description is None

[5367] by k0s on 03/18/09 15:13:41

give URL of TracBacks? home page in setup.py

[5151] by mchua on 01/23/09 03:30:56

mixedpuppy's patch; check for trackbacks on ticket creation

[5150] by mchua on 01/23/09 03:27:48

mixedpuppy's patch for ticket:NNN link format support

Author/Contributors

Author: mchua
Maintainer: ?
Contributors: tcoulter (original proposer), Doug Mayle, magicbronson, k0s

Originally written at The Open Planning Project.