Hi,

We'd like to use the ticketsubmitpolicy plugin in our Trac and Agilo
installation. We've modified it so that it'll highlight mandatory
fields as well as leveraging its ability to "require" certain fields
be filled in before the ticket edit can be submitted. We do this
because it's not sufficient for us to have a mandatory field have a
default value... we want our users to actively decide on a field's
value so that the data being collected is high-quality.

This plugin, of course, doesn't work as is, because it depends on
trac.ticket.web_ui.ticketmodule, which must be disabled for Agilo to
work.

My question is, has anyone successfully accomplished code changes that
get the two to work together, and if so, are you willing to share the
changes? Or if you know right off the best approach to do this, please
let me know. I have no problems sharing the changes if we do manage to
get it working. I just don't want it to take too much of my time away
from other projects.

Thanks.

-- 
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
Please support us by reviewing and voting on: 
http://userstories.com/products/8-agilo-for-scrum 
http://ohloh.net/p/agilo-scrum 
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Scrum" Google Group. This group is focused on
supporting Agilo for Scrum users and is moderated by
agile42 GmbH <http://www.agile42.com>.

To post to this group, send email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo

Reply via email to