5/11    Hi guys.  Is JIRA all that?  We have Bugzilla too, but JIRA looks nice,
        and we can afford it.  Thanks.
        \_ It was the leading candidate in our attempt to replace Bugzilla,
           but there were enough problems with it that we decided not to use
           it. (The status of the replacement project is undetermined.) My
           biggest complaint was that the search interface sucks, both in
           terms of UI and power. I also didn't much care for the fact that
           email preferences are per-project and not per-user, so I can't
           adjust when I get email. The lack of Bugzilla's "watch user"
           feature is a problem too; although some aspects of notification
           schemas are better than user watching, they don't cover the same
           set of features. I also just didn't like the UI -- every action
           requires opening a new page, it's clunky, important information
           isn't presented very well, and it keeps rather more state than
           I would like (so clicking on one link, clicking a second link,
           and clicking the first link again doesn't bring me back to the
           same page). It seems like it's not well built for the way we work.
           There are features we like, just not enough to overcome the things
           we didn't like. -gm
           \_ We switched to JIRA. All the things that gm doesn't like, except
              for the back page stuff, you can control by setting up custom
              work flows. This takes time though. -ausman
              \_ Thanks guys.