[Trac] Re: Retesting procedure in Trac
Take a look at the workflow branch. It allows for modifying the ticket workflow both from trac.ini and a plugin. --Noah On Oct 9, 2006, at 4:19 AM, Cees wrote: Is it possible to extend the life-cycle flow of a ticket with a retesting cycle? Is it possible to extend the list of states of a ticket? I have been looking around for it but I cannot find it. With kind regards, Cees --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~--~~~~--~~--~--~---
[Trac] Re: Retesting procedure in Trac
On Mon, Oct 09, 2006 at 10:25:49AM +0200, Christian Boos wrote: The WorkFlow branch will provide support for this kind of things, in a simple configurable way. We're all eager to know when Alec will resume his work on the branch (big painful merge ahead ;) ) Yay fun! Are we actually in a state where I can restart work on this? ie. is trunk stable enough to work against? I'd like to avoid having to merge with a constantly moving target if possible. This was the main reason I stopped updating WorkFlow before 0.10 - many many changes to the ticket module. -- Evolution: Taking care of those too stupid to take care of themselves. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~--~~~~--~~--~--~---
[Trac] Re: Retesting procedure in Trac
Alec Thomas wrote: On Mon, Oct 09, 2006 at 10:25:49AM +0200, Christian Boos wrote: The WorkFlow branch will provide support for this kind of things, in a simple configurable way. We're all eager to know when Alec will resume his work on the branch (big painful merge ahead ;) ) Yay fun! Are we actually in a state where I can restart work on this? ie. is trunk stable enough to work against? I'd like to avoid having to merge with a constantly moving target if possible. This was the main reason I stopped updating WorkFlow before 0.10 - many many changes to the ticket module. I'd say yes. AFAIK, there's nothing which will affect directly the ticket subsystem, and the remaining things to be done for 0.11 shouldn't have too much impact on it either: - the datetime changes will change the time fields to datetime objects instead of timestamps - the setuptools adaptation will also affect the ticket subsystem like any other subsystem, but in this case, it means shuffling files around; not a big deal to merge. - on the Genshi level, there's still some work to do for enabling plugins to filter the page content, somehow. The workflow ticket plugins may be able to take advantage of this once the mechanism is there, like for adding/removing fields. But for a start, the way you did it on the WorkFlow branch should be good enough. This could always be improved later on. -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~--~~~~--~~--~--~---
