Changes between Version 5 and Version 6 of ChildTicketsPlugin
- Oct 15, 2010, 8:06:27 PM (6 years ago)
v5 v6 2 2 3 3 = Support for pseudo child-tickets and a visual reference to these within a parent ticket. = 4 5 '''''NOTE @ 19/04/2010:''' I have just been looking through the proposals for future support of Parent/Child tickets in trac core ([http://trac.edgewall.org/wiki/SubTickets SubTickets]) and want to point out that this plugin proved useful for my old dev team (and _old_ firm) but I've not tried to provide any kind of resolution for [trac:ticket:31] nor [trac:ticket:886]. From one of the last comments on [trac:ticket:886] I see that itota has also recently published a very similar plugin, SubticketsPlugin. I plan to collect the features of this plugin and raise them as new issues/features for itota's SubticketsPlugin - it makes little sense to have more than one plugin doing the same job (and I quite like itota's simpler child-ticket list in the parent ticket.)'' 6 4 7 5 == Description == … … 20 18 * to define whether the parent milestone is adopted by child tickets or not 21 19 22 Under Trac 0.10 I had to modify the ticket.html templates to get this working in any 'pretty' sense so I have not provided support for 0.10. As of 0.11, the ITemplateStreamFilter allows this to be incorporated nicely into a neat plugin. I have not tried it with 0.12 yet. 20 Under Trac 0.10 I had to modify the ticket.html templates to get this working in any 'pretty' sense so I have not provided support for 0.10. As of 0.11, the ITemplateStreamFilter allows this to be incorporated nicely into a neat plugin. 23 21 24 22 In order to keep the plugin as compact and simple as possible and to allow future compatibility with different CSS schemes, I have simply 'pinched' the existing CSS classes for generating the table and its components.