When thinking about subtasks, one of the issues that comes up is propagating
changes from child to parent. If you use subtasks with Time and Estimation,
you likely want a parent task's estimate to be the sum of it's children's
estimates. If you assign Start or Finish dates to children, you likely want
the parent to start when the earlieast child starts and finish when the latest
child ends.
I'm considering writing a generic ticket attribute propagation plugin. This
would implement a configurable Ticket Change listener capabale of doing the
updates described above. Configuration might look like:
[attribute_propagate]
parent.fields=start, finish, estimate, work
parent.start.method=min
parent.finish.method=max
parent.estimate.method=sum
parent.work.method=sum
Which means: when a ticket changes, if the parent field is not empty, use it to
find another ticket and update its start, finish, estimate, and work fields.
Start is updated as the minimum of the current ticket's start and the other
ticket's start. Finish as a max. The other ticket's estimate would be it's
value minus the current ticket's old value plus the current ticket's new value.
I hope you get the idea.
This doesn't seem too complex and I'm ready to dig in but if there's a plugin
that does something like this already, I'd rather same the time. Any thoughts?
Chris
--
Christopher Nelson, Software Engineering Manager
SIXNET - Solutions for Your Industrial Networking Challenges
331 Ushers Road, Ballston Lake, NY 12019
Tel: +1.518.877.5173, Fax: +1.518.877.8346 www.sixnet.com
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
