On 2/22/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote: > I've read a little within the trac wiki, but get confused of how the > status is. > > Are there any methods to model ticket-dependencies (depends-on <-> blocks)?
I think that depends on the level of functionality you want. I imagine the simplest possible solution to this is just adding a custom field where you can reference the other tickets and then do searches based on this. Can you describe your requirements a bit further? Maybe you can add something useful to the #886 ticket which is probably the one describing this? Reading the wiki I can understand you gets confused. An old-ish attempt at enhancing the tickets is at NewWorkFlow, but quite recently athomas has been working on providing some good ticket extension points in WorkFlow =:-) In between this cboos has maintained the TracCrossReferences branch for quite a while now. This code targets a much wider problem area than ticket dependencies. To sum it up everything for 0.9 or trunk versions is a work in progress AFAIK. My best bet would be that if you want to implement something yourself you should write a plugin and base it on athomas' WorkFlow branch, see [1] and the trac-dev mailing list for a head start. If you on the other hand want's something quite sofisticated and don't want to code the CrossReferences branch might be your favorite. [1] http://projects.edgewall.com/trac/wiki/WorkFlow#ExampleManipulator -- JornH _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
