Dana V. Baldwin wrote: > I'm wondering if anyone can help improve my process with TRAC. > > I run an MMOG and use TRAC to manage tickets for features, tasks and > bugs. I currently have several projects but as they are all for one team > I keep them all in the same TRAC environment so I can track owners tasks > across multiple projects, separating them with milestones. > > Currently when a ticket is complete, it needs to be tested in a release > build. I'm currently managing this by changing the user to test. This > has the benefit of keeping all of my test tickets together but is a > burden to accountability for the original owner. > > Is there a better process for flagging tickets that are ready to be tested? >
A good alternative here is to use the ticket-workflow section of trac.ini to define a new state "done" or "needstesting". You can then make it so devels can not resolve tickets, only set them to "done", then you (or someone w/ proper prerms) can query everything in this state and change them to closed/resolved with a resolution of "tested" (you can easily create custom resolutions in trac). This is what I am doing for our trac (still in the process of testing/research), but keep in mind I am using 0.11 and I am not sure of the status of some of these features in 0.10.x. Best, Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
