I'll second the opinion, Kurt. We use OnTime to manage several regional offices from Dubai to Hong Kong, as well as our Australian office (where I'm based), using OnTime for call management.
We're using an ITIL-based process which classes calls into Incidents, Changes (eg. Features) and Issues (aka bugs). All calls come in as Incidents, and are then triaged by the Support Desk. If a call relates to new functionality it's cloned to Changes, if a defect to Issues. The workflow automation allows us to track what stage calls are at, to enforce mandatory information to be keyed in by the person handling the call, to track the work hours expended, and to drive the sort of business intelligence reporting our bar-graph besotted upper management crave. The users have adopted OnTime well, with no more than the expected resistance which occurs when people are ... encouraged, shall we say, to work in a more formatted, organised manner.
We're a SQL house here, so we've ignored the OnTime report tools to use MS Reporting Services, which lets us churn out more or less anything that can be specified, depending on how much time we want someone to spend on playing with queries & tables.
We had a look at a number of other support desk packages, including some tens of times more expensive. OnTIme hits a happy medium between the cheaper "here's a pile of parts, build whatever you want" solutions, and the "please book ten hotel rooms for the implementation team" higher-end packages.
Cheers,
John H