On 1 October 2010 04:02, Mark Mc Mahon <mtnbikingm...@gmail.com> wrote: > Hi, > > On Thu, Sep 23, 2010 at 10:23 PM, Mat Booth <t...@matbooth.co.uk> wrote: >> In case anyone is interested, I wrote a plug-in to make any standard >> field or custom field required based on arbitrary boolean expressions >> that can be configured in an admin panel. >> >> For example, in the Trac instance I manage, I have a testing field. My >> plug-in allows you to say "make testing a required field when (status >> == closed && resolution != duplicate)" to force the user to fill in >> the custom testing field when they close a ticket that isn't a >> duplicate. >> >> http://www.matbooth.co.uk/trac/wiki/TicketValidationStart >> > > Yes that is very cool :) >
Thanks to everyone for the kind words. :-) > From the quick play I had with it - it works very well. (with custom fields > etc) > > Are you suggesting that it may be integrated into Trac core? If so > then it would probably need modification to fit in (Trac may not want > PyParsing as a dependency for example). > At the time, using a library was the quickest way to get the plug-in into shape for use on our production Trac system. As Remy said, it would be possible to write a simple expression parser to eliminate that dependency if necessary. > Also more documentation would be good - I would not have figured out > that status conditions conditions are supported without the example in > your previous email. > You're absolutely right, my documentation sucks. I will try to fix that soon :-) Regards, Mat -- Mat Booth -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-...@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
