On May 8, 10:30 am, Greg Troxel <[email protected]> wrote:
> Chris Nelson <[email protected]> writes:
> > Greg Troxel wrote:
> >> I am currently using 0.11.4 with MasterTickets and
> >> TimingAndEstimation.
>
> > Me, too.
>
> >> We use blocking/blocked-by for two separate meanings:
>
> >> Can't do X until Y is done.
>
> >> Ticket A comprises subtasks AA AB AC AD AE.
>
> >> The second case is exactly what you need to represent a Work Breakdown
> >> Structure in trac.
>
we do this now. same scenarios, we have "blocking" tickets, and
"feature" tickets, a feature is blocked by a bunch of related tasks,
defects and enhancments etc.
I created a template I use for a "feature ticket", in my case I just
cut and paste/modify. you could of course use one of the plugins for
ticket templates.
My template has 2 things, the "progressMeter" macro, for all tickets
where "blocking" contains (this ticket number), then I don't need a
milestone for this feature ticket. (although, lately we have been
doing this anyway, then our "release" milestones ONLY contain feature
tickets....that's a different story)
The second thing in the template, is I have the estimationtools plugin
installed. I have test that says: Total remaining hours of child
tickets: [[HoursRemaining(blocking~=THIS TICKET NUMBER) !check syntax
there etc, that was pseudo macro speak!
I suppose with 0.11.4+ this could actually be a field that supports
wiki markup, I like it in the description section under my
"progressmeter"
As a bonus, I get the depgraph for free. Is is slightly clunky? yes.
I should probably make a ticket template, so that the "field": I
mentioned could be auto-populated with "this" ticket number
automagically.(tm) however, my html/.css is non-existent, and
surprisingly, I really have no interest at all to change that :D
as for reports/exporting, you could then just use the
TimingandEsitmation tools reports page, make the Total remaining hours
of child tickets: label a link to the query that would report for that
ticket only, and you get THAT for free too:D I personally create a
wiki page for each "feature" since we don't have a large number, and
embed this kind of information there with some other stuff for the
"corporate" types so I can point/train them to go look there first
before firing off an email to the world with a question that can be
answered by just reading said "feature" page.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
