Hi Paul, We are on the same boat. I have been trying to learn how to write a plugin for a month. I haven't had much time to spend on it until the summer. What I have been doing is to read existing plugin code. Perhaps we should create F&Q page in the hack website regarding how to start hacking Trac.
As for your question, I have also thought about that. I think it is possible to do what you want using existing plugins, but it might not be exactly what you want. Here is the configuration I have in mind (haven't tried) 1) Use MasterTicketPlugin. This plugin allow you to link tickets together as parent/child. Similar to block/depend in Bugzilla 2) Use TimingandestimationPlugin. This plugin allows you to keep track of hours spents on ticket. 3) Create WBS as task type ticket then link them to the main ticket of type enhancement (new feature). As for PBS, I think you might have to implement it as plugin since component field can't represent hierarchical structure. If you get to work on it please keep in touch. The plugin that I am working on is focusing on getting the information from Trac that are useful for project planning and tracking. One Trac feature that I was hoping for the ticket is to be able to change content of a custom ticket field based on the value of main ticket field. If this is possible, you could create custom field named "sub component". The content of it will changes based on the value of the component field. -- Deen On 5/2/07, Paul Cohen <[EMAIL PROTECTED]> wrote: > > > Hi, > > Is there any Trac hack/module for creating and maintaining WBS (Work > Breakdown Structure) and/or PBS (Product Breakdown Structure)? > > To give you a picture of how I see things: I see the current handling > of components in Trac as a (very) simple PBS-tool. I see WBS as as the > base of all project planning and management. I see tickets as a way of > capturing things to be done that weren't originally planned. Having > said that I don't believe in over-detailed planning. I believe a in > sound planning *and* daily capturing of new (lesser) requirements and > issues to deal with. > > To begin with I'm interested in being able to: > > 1. Replace the current handling of components with a more fully > fledged PBS support. > 2. Set properties of PBS nodes. Eg: "owner", "platform". > 3. Create and maintain heirarchical WBS structures of arbitrary depth. > 4. Set properties of WBS nodes. Eg: "owner", "estimated time to > completion", "priority level" > 5. Assign WBS nodes as belonging to a given PBS-node/component. > 6. A given WBS should be able to be marked as belonging to a given > Milestone. > 7. Have multiple WBS:s in a given Trac-project. > > In addition I would of course like to: > > 1. Derive computed "estimate time to completion" for higher level WBS > nodes, using different cost estimation models, preferably via some > plug-in mechanism. > 2. Use a WBS as a base for time reporting. > > Maybe I have to write it myself! :-) What is is the most important > documentation to read before starting to hack Trac? > > /Paul > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
