5/12    Anyone here use THE JIRA for issue tracking? How much does it suck?
        \_ Don't really use it.  Our team evaluated it and decided in
           favor of Bugzilla.  Bugzilla doesn't cost $2k--though cost
           is negligible.  The real deciding factor was that in my
           environment it can take 6 months to deply software not
           already on an 'approved' list, and Bugzilla was already
           on that list and JIRA was not.  At the time of evaluation,
           JIRA had no support for SVN interoperation, but that
           has since changed.  I realize this answer is mostly useless,
           but hey, at least someone cared.
        \_ I'm spearheading an effort to install it into our process.
           It has a lot more features than Bugzilla.  The SVN integration
           you buy with a different product, Fisheye.  The downside:
           JIRA is written in Java, and sometimes throws stack traces.
           We have yet to lose any data though.
        \_ I worked at a place that went from Bugzilla and wiki to JIRA
           and Confluence and while the transition was quite a bit of work,
           the end result justified it. Out of the box, it is as good and
           has a bunch of cool work flow stuff you can put in there to make
           you and your managers life a lot easier. Setting up the work flow
           is a big job though, so if you just want a ticket tracking system,
           I don't know why you would switch.
        \_ whats wrong w/ trac? ... esp if you want great svn integration.