> -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > On Behalf Of Daevid Vincent > Sent: Monday, June 09, 2008 4:45 PM > To: [email protected] > Subject: [Trac] "fixed" is NOT the same as "closed" > > > Wait a minute! > > I just realized that when a developer resolves a ticket as "fixed", > Trac > sets the status to "closed"! > > Those two things are NOT the same. "fixes" SHOULD mean that a tester > can now > go and verify the fix. > ONLY the tester should be able to "close" a ticket. > > * status changed from new to closed. > * resolution set to fixed. > > In fact, I don't even see a "status" field that I can manipulate. Where > the > heck did status come from? > > How can we prevent this non-standard behavior?
While one can argue the semantics of a "standard" workflow, the TracWorkflow page has details on setting up a custom workflow using either the included (and simple) trac.ini-based syntax, or developing a more complex plugin to provide ticket actions. You cannot alter the status of a ticket directly, it is manipulated by workflow actions. --Noah --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
