support for mastertickets

[Jeff Hammel]

If the MasterTicketsPlugin is used in conjunction with the TracHoursPlugin the total hours from "child" tickets could be counted towards a master ticket

[anonymous]

this also holds for TicketDepPlugin?

[Jeff Hammel]

deprioritizing; this is clearly after 1.0 for TracHoursPlugin

[Ryan J Ollos]

Reassigning ticket to new maintainer.

[Daniel Abel]

Support for SubticketsPlugin would be nice, too. (I will most likely end up using TimingAndEstimationPlugin and SubticketsPlugin with ValuePropagationPlugin to allow such aggregation to work, instead of TracHoursPlugin, even though on its own, TracHoursPlugin looks better than TimingAndEstimationPlugin due to better design and having less of a 'hackish' feel)

Some extra notes that might be interesting when implementing this:

• solution should aggregate not only logged hours, but also planned hours (i.e. the estimates, too)
• It should allow estimates & hours to be specified for the 'master ticket' (i.e. master tickets's hours is not only the sum of the subtickets', it can be more.)

[Ryan J Ollos]

Replying to abeld:

TracHoursPlugin looks better than TimingAndEstimationPlugin due to better design and having less of a 'hackish' feel)

I haven't used TnE plugin, but the significant factor that led to my decision to use (and subsequently adopt and further develop) the TracHoursPlugin was that TnE appears to be more suitable for working with external clients (tracking hours to bill), whereas TracHoursPlugin is well suited for tracking hours on internal projects. I'd be interested to hear your comments if you have experience with both.

[EmeCas]

Reassigning to maintainer