On Wed, Apr 8, 2009 at 4:06 PM, Chris Nelson <[email protected]> wrote: > > I'd like to gather the requirements for it.
:o) > Is it best to do it in a thread on this mailing list or start a wiki page at > Trac-Hacks ? > both ;o) -1 for tickets, so far ... > I'll start here and if this isn't the right forum, we can copy my comments to > whereever they belong. > wiki page > A Gantt plugin for Trac should analyze ticket dependencies and produce an > interactive, explorable Gantt chart showing task progress and project status. > +1 > By "project", I mean a set of related milestones. Milestones *SHOULD* be represented in the diagram as a single point at due time | date > Perhaps a software project has a Design Phase, an Alpha Release, a Beta >Release, and a General Release. Each would be a milestone with a target date >and tickets to complete the work for that milestone. There must be a way to >specify which milestones to include either listing explicitly +1 > or by giving a pattern or substring filter. > +0.5 > The chart should be able to show all tickets, though that may be a very > complex chart. > or alternately all those tickets matched by a (query | report) or any other ticket group provider ;) > The chart should support interactively "folding" groups of tasks to hide > detail. > +1 > Tasks/tickets in the chart should be links to the tickets they represent. > +1 > To effectively display project progress, tickets must have estimated and > actual times as in the TimingAndEstimation plugin. Is this sched vs execution (plan vs real progress ;) time? > Each task's bar in the chart should show actual hours. > +0 > The chart should have a Today line > +1 > Ticket dependencies that must be supported include: > > 1. Task B must follow task A. > 2. Task A is composed of tasks B and C. A's estimated time is the total of > B's and C's. What does this means exactly ? How will it be represented in the chart? Two many lines is annoying ... > 3. Tasks A and B start at the same time > 4. Tasks A and B must end at the same time > +1 > Type 1 dependency is implemented in the MasterTicket plugin. Note that a > task may have many predecessors and many successors. > > Type 2 dependency is necessary to support "folding" or "zooming" detail in > the chart. It is also generally useful and might be implemented as its own > plugin that the Gantt chart could require. Note that is should be possible > to create a tree where A is composed of B and C, and B is composed of D and > E, and C is composed of F, G, and H. > About providing the data to Gantt plugin and the interaction with other plugins, specific interfaces (dont know if they'r already there ;) should be included in order to gather the data about WBS and deps, and so on. I mean instead of requiring a plugin, IMHO it is better to say «if you want to render data in your Gantt chart, implement interfaces X, Y, Z and config» instead of «Gantt plgin depends on plgin X, Y, Z». This also means that users will be able to use their own estimation and deps algos if they want to. > Types 3 and 4 are more unusual and a useful Gantt chart can be created > without immediate support for these links in the first release. > +1 ... > It is also desirable to have loop detection to error-proof the tool used to > create dependencies. > hmmm ... perhaps stated like this : «loops and other errors should be highlighted in the graph» > It would be nice to be able to choose an As Late As Possible or As Soon As > Possible algorithm for laying out tasks. > IMHO this should be left to other plugins (components), in order to allow different approaches (perhaps providing a default impl, ok I agree) > The chart (or an accompanying report or tool) should aid in resource leveling > by (at least) showing overcommitted resources. > But this is a completely different & potentially complex (yet useful) development needed. Perhaps it should be deferred ... practical dev is important ;) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Se retira el BDFL ... ¿El fin de Python 3k? - http://feedproxy.google.com/~r/simelo-es/~3/HpncxTKfB1c/se-retira-el-bdfl-el-fin-de-python-3k_02.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
