title: grails, drools, and ticket / issue trackers, iTicket
body: <p>I need to integrate a ticketing system into my grails Web application, so that those running the small company can easily handle customer needs / complaints, etc., tying that in directly with their users. When I searched for a plugin or built application, I found:</p>
  
  <ul>
  <li><a href="http://www.grails.org/plugin/drools" rel="nofollow">drools plugin</a>, small ticketing capability/example, which after having an installation bug led me to</li>
  <li><a href="http://www.grails.org/Drools+Plugin" rel="nofollow">drools-gorm plugin</a>, and then also briefly reviewing </li>
  <li><a href="http://groovysource.com/open-source/issue-trackers/i-ticket" rel="nofollow">iTicket</a>, which I'm just currently shying away from because of its inclusion of roles management but no mention of Spring Security Core and UI, which is what I'm using for role management</li>
  <li><a href="http://josh-in-antarctica.blogspot.com/2008/04/writing-simple-issue-tracker-in-grails.html" rel="nofollow">article on building a small issue tracker with Grails</a></li>
  </ul>
  
  <p>I don't have a lot of problem domain knowledge with ticketing systems, and so I'm wondering if someone whose gone down this road before or knows ticketing system domain modelling &amp; rules engines in general can give a few comments.  E.g. are flexible rules engines very important for ticketing systems, or is this only for heavier weight applications?  What kinds of other general things can one do with grails plus drools, that might be useful?  Alternatively, the opposite, is staying light weight best, because these things often turn out to be very "custom" in this arena.  </p>
  
  <p>Your experience is appreciated.    </p>
  
  <p>Thanks</p>