On Tue, Jun 03, 2008 at 01:21:18AM +0200, [EMAIL PROTECTED] wrote: > > Hello, > > considering all the plugins that try to hide, extend, modify or play > with the custom properties of a ticket, and also reading through the > resent discussion about the trac core I have a simple question to > understand a design decision. <snip/>
Coincidentally in time, I have been working on a plugin that enforces a ticket submission policy based upon field values (ticket type being one of the obvious choices): http://trac-hacks.org/wiki/TicketSubmitPolicyPlugin . The code is a bit hacky, as I haven't had time to clean it up yet, but the general idea is that fields can be required or hidden via JS according to configuration depending on other field values. I'd like it to be more flexible going forward, but that's more there than here. In my glancing at trac-hacks.org, I didn't see anything that fit this bill. Did I miss a plugin or two? Did I reinvent the wheel here? Or is this actually useful? I didn't really look at this as providing different "types" of tickets per se, but it is a solution for us (http://topp.openplans.org) to that effect. But I'd like to know what other people do for this issue. Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
