I’ve used DevTrack a bit. Rather, I’ve used their API and integrated it into one of our key QA tools. I have not used the tool itself as a front-facing user, so just making that clear.
Some background… We have an in-house tool that logs in-game locations and screenshots to a database. It also integrates with Hansoft (our bug tracking weapon of choice ATM), and can create bugs and populate them with sensible values/attachments. Our corporate QA department uses DevTrack instead of Hansoft, so in order for them to benefit from our location-logging tool I had to add DevTrack integration as well.
Out of the box, DevTrack doesn’t have a usable API for integrating it with other tools. To do that you need to purchase a separate license for their LinkPlus module. LinkPlus uses a SOAP-based webservice as its only interface. It’s very much like regular web programming where you’re submitting requests, sometimes waiting longer than you’d like, then getting responses back that require parsing, etc. I had to learn a fair amount about dealing with SOAP responses in Python, turning error codes into friendly messages, generally through a lot of trial-and-error. It was tedious at first, but not terribly complex.
At the end of the day I was about as ambivalent about DevTrack as an overall tool as I am about Hansoft. Same goes for their APIs. When it comes to bug tracking software, I think your favorite band sucks. They’re all good at some things, and shockingly bad, but in different ways.
I’d suggest just getting LinkPlus up and running, along with the thing that lets you test their API calls right from a webform. It’s not awesome but without that I would have thrown it straight out the window. When you get into the dirty bits let me know and I can probably help you out on the specifics.