Changes between Version 1 and Version 2 of TracDev/Proposals/TicketLinks
- Timestamp:
- Nov 25, 2014, 10:39:45 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/Proposals/TicketLinks
v1 v2 3 3 This proposals corresponds to the implementation of #31 and the related tickets, like #886/#9550. 4 4 5 The work started on this topic by bootstrapped by the [ repos:66f599dd26c8/ticket-links patch] contributed by Joachim Hoessler on that ticket.5 The work started on this topic by bootstrapped by the [changeset:66f599dd26c8/ticket-links patch] contributed by Joachim Hoessler on that ticket. 6 6 7 7 The approach from this patch was preferred over the ones from existing plugins (TH:MasterTicketsPlugin, TH:SubticketsPlugin, TH:ChildTicketsPlugin) as none was providing a really extensible starting point, in the spirit of #31. The first two use a specific table dedicated to the relation they're dealing with (respectively `mastertickets(source, dest)`, `subtickets(parent,child)`), and the latter is using a `parent` custom field. That is not to say there are no interesting ideas to lift from there ;-) … … 12 12 13 13 The TicketLinks page describes the work in progress in the [repos:ticket-links] Mercurial branch. 14 15 ---- 16 Note that this approach has stalled, in part because I couldn't find a good way to integrate this with the TicketQuery module. Lack of global approach for dealing with multi-valued fields... #918. -- //cboos, 2014//