Thanks! On Wed, Jan 7, 2009 at 3:02 AM, jevans <[email protected]> wrote: > > > On Jan 6, 5:27 pm, Greg <[email protected]> wrote: >> Hi, >> >> I'm a potential future user of Trac, currently using Bugzilla, and I >> have a question about Trac's workflow customization. >> >> My company currently tracks bugs and features. While I like the idea >> of considering both bugs and features as subsets of a single "issue" >> concept, we need to use different terminology for the two. For >> instance, bugs would have states like "reported", "confirmed", >> "assigned", "fixed", and "closed", while features would have states >> like "requested", "approved", "assigned", "completed", "tested", and >> "merged". The reason for the distinction is partly to avoid confusing >> our staff, and partly for regulatory compliance. >> >> Would I be able to configure a single installation of Trac to handle >> these two different workflows, or would I be better off to install >> Trac twice? >> >> Thanks, >> >> Greg > > Speculation: > Perhaps the TicketCreationStatus plug-in (<http://trac-hacks.org/wiki/ > TicketCreationStatusPlugin>) could be extended to support setting the > initial state based on ticket type. Or it might be useful as a > starting point for a separate plug-in that does it. I think setting > up separate workflows from there would be pretty straight-forward. > Good luck, > - jevans > > >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
