|Version 15 (modified by rjollos, 4 years ago) (diff)|
Backlinks for tickets in comment history
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
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.
Download and Source
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
-  by ejucovy on 2012-10-18 17:04:35
close #9008 -- In the event that the changelog is empty, cnum_thischange needs to be set to the string "1", not the integer 1
-  by ejucovy on 2012-10-01 01:52:35
ticket.get_changelog() returns entries that aren't comments (as well as entries that are comments) -- so, if the latest modification on the ticket does not have a comment, tracbacks will cause an internal error by assuming an incorrect data structure. this commit fixes the problem by filtering out all changelog entries that are not comments. (fixes #9743)
-  by rjollos on 2012-09-12 07:37:50
Fixes #9809: (0.2dev) Changed license from GPLv3+ to 3-Clause BSD.
Originally written at The Open Planning Project.