> This is interesting, but I think adding a new "type" for every potential > use somebody comes up with for a ticket field is going to become > unwieldy quite quickly.
I think you're right. > Having a ".onchange" property added to the custom fields might be a more > flexible solution, allowing people to add arbitrary JS logic to their > custom templates. In conjunction with the (hopefully imminent) workflow > changes this would allow field validation through both JavaScript and > Python. +1. Nice idea. -- Manu _______________________________________________ Trac-dev mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac-dev
