http://trac.edgewall.org/wiki/TracWorkflow
or, more explicitly (from link) 0.10 default: http://trac.edgewall.org/browser/trunk/trac/htdocs/original-workflow.png 0.11 default: http://trac.edgewall.org/browser/trunk/trac/htdocs/basic-workflow.png James James Guyton (JGU) From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Howell Sent: Monday, September 10, 2007 4:33 PM To: [email protected] Subject: [Trac] Re: problem with w/f Is there a document I can refer to for Trac .11 W/F so that I can discuss it here at work and why I shouldn't change it and we should just wait for Trac. 11 to be released ? Cheers Chris Chris Howell wrote: I am not seeing anything different with the w/f in Trac .11, Chris James Guyton wrote: Just an offhand estimate, backporting the workflow to 0.10 would be orders of magnitude (yes, orders of magnitude) more difficult than checking out the Dev branch(yay svn), installing it (python setup.py install, if I recall correctly), and restarting the service. Of course, this is if you are using tracd; no idea what is needed for Apache users. There are other significant improvements to Trac which would be missing as well. However, there is an intermediate state between new and closed, the "assigned" state. As an intermediary measure, have your developers accept the tickets, and when they have implemented a fix, have them assign the ticket to either a specific tester or team lead (it goes back to "new" at this point, I believe), who would accept the ticket, evaluate/test and actually deem the issue "fixed" (thereby putting the issue into "closed" state). James Guyton (JGU) -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Howell Sent: Monday, September 10, 2007 3:08 PM To: [email protected] Subject: [Trac] Re: problem with w/f Upgrading to Trac .11(Dev) would be great but I don't really have the time to build it for Windows. I've got my own development wrok to get done. Jennifer A. Drummond wrote: On Mon, Sep 10, 2007 at 11:45:26AM -0700, satyendra wrote: Trac has no intermediate states for issues between new and closed, as soon as a developer fixes problem and changes the the resolution to "fixed" trac closes the bug. Ideally I would like to change the resiolution to fixed and have the tester validate the fix and then close it, is there an easy way to change w/f to accomplish this. -satyendra The easy way is to upgrade to 0.11dev; I don't know if there's a hard way! Seriously, the not-yet-released 0.11 version has spectacularly configurable workflow. We're using it in production and love it. But I don't know if the workflow customizer can be backported to 0.10 at all. Anyone else? =-=-> Jenn Drummond // [EMAIL PROTECTED] Project Developer, Connexions Project (cnx.org) Rice University --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
