I recently installed MasterTicketsPlugin but have not installed Graphviz. I also do not find the graphs to be very informative. I do like what TicketDep describes but I have not been successful in getting it to run.
I have the TracTicketDep-0.11_20081224-py2.4.egg file installed in our Trac plugins directory but I cannot get it to function. Do I need to add something into the trac.ini [components]? I tried adding "tracticketdep.* = enabled" and "ticketdep.* = enabled" but neither of these helped. I did stop and start our apache2 server when trying each entry. Here is our environment: Trac: 0.11.2 Python: 2.5.1 (r251:54863, Sep 21 2007, 22:46:31) [GCC 4.2.1 (SUSE Linux)] setuptools: 0.6c8 MySQL: server: "5.0.67-community", client: "5.0.67", thread-safe: 0 MySQLdb: 1.2.2 Genshi: 0.5.1 mod_python: 3.3.1 Subversion: 1.5.5 (r34862) jQuery: 1.2.6 Thank you. On Dec 24 2008, 7:36 am, Risto Kankkunen <[email protected]> wrote: > Our team uses Trac to manage our sprint backlogs. We find it useful to > split bigger tasks into subtasks and use MasterTicketsPlugin to track > the dependencies. However, it is currently not easy to see those > dependencies. The Graphviz diagrams require effort to see and are not > even very informative. > > I made a plugin calledTicketDepthat shows the dependencies as > indented tables. After using the plugin for some time I find that it > helps to see the context of a particular ticket and also makes it > easier to find the right parent for new subtickets. The plugin is > available in > > http://iki.fi/risto.kankkunen/trac/ticketdep > > I'd like to hear if people find this useful and if someone has already > done something similar. > > However, the main reason I'm writing about this plugin is that I'd > like to find a maintainer for it. I don't really have time to take > care of it. I hope it is useful for other people already now, but on > the other hand I don't want to offer it without any support; I have > been bitten too many times taking some plugin from trac-hacks into use > and later having found out it was not maintained, stopped working when > a new Trac version came out etc. > > While making this and some other plugins, I found myself wanting to > chain plugins together in a pipeline. Even inTicketDepI ended up > calling some internal functions of TicketQuery. I would have preferred > to do something akin to [[TicketQuery |TicketDep]]. I've also seen > some other plugins where I liked the way plugin A displayed its > results, but liked more how plugin B calculated them. But since I > couldn't choose A's display and B's logic, I had to make my own plugin > C... It would have helped if A was actually [[Acalc | Adisplay]] and B > was [[Bcalc | Bdisplay]] so I could do [[Bcalc | Adisplay]]. > > Has anyone given any thought of how plugins could be made composable? > > Risto --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
