Support ChildTicketPlugin for dependencies

[Jay]

Cool plugin, very useful.

It would be great if there were a way to all the plugin to work with the ChildTicketsPlugin for dependencies.

This plugin fills in it's "dependent" tickets dynamically and in the description field, not as a field list in the ticket itself. Also, the revers view, a ticket's "parent" is wiki formatted (#12345) vs a plain text filed without the '#'

Thanks.

[anonymous]

ChildTicketsPlugin is being dropped (per the owner's comment) in favor of SubticketsPlugin - and it would be awesome if it would work with that.

[Andreas]

Very good suggestion. I will implement an integraton of the SubticketsPlugin soon.

[Ryan J Ollos]

I'll be adding the functionality of the SubticketsPlugin to MasterTicketsPlugin (which currently handles blocker/depends relationships), so you may be interested in that work as well: #3613.

[Jonathan Laufersweiler]

This might be worth revisiting.

I currently have a Trac 1.3.2 instance up and running, and ChildTicketsPlugin installed and ran in that environment successfully with no modifications. In contrast, when I look into SubticketsPlugin's source I see things like TicketNotifyEmail which were deprecated in 1.2 and have been dropped from 1.3.

Further, since ChildTicketsPlugin uses Ticket-Custom fields rather than a separate table as SubticketsPlugin and MasterTicketsPlugin do, parentage is exposed/setable/editable to the Mylyn Trac-Connector for EclipseIDE, which does not see custom tables.

Current trunk & T1RA branches both seem to be gravitating towards integration with the mastertickets table though. Is there yet a way forward for a single dependancies field approach?