This question covers bug tracking software in general, but I'm interested to find out more detail specifically about Devtrack.
If you have first-hand experience of using it, I'd love to hear about it. How would you compare it to other bug tracking systems you know, what do you feel is good and bad about it, and why?
I used it when I worked at Electronic Arts Tiburon ... IMO, the UI is clunky and entering/managing bugs is time consuming. Depending on what environment you're using, I'd look into either:
We also used DevTrack for years and switched to Software Planner (http://www.SoftwarePlanner.com) about a year ago and are a lot happier.
DevTrack is being pushed out in some areas of my company. I've heard two things: it's ok once you get used to it, or it's a painful/tedious experience. My current impression is that it has more support at the "decision maker" level than it does at the developer level.
Not sure how to bump this, but would like to get this question to a fresh set of eyes now that it has been over half a year. Any further thoughts from anyone?
we've always found that we end up duplicating a lot of work by using devtrack. For developers it's generally a pain to use particularly when trying to keep a history or knowledge base of an applications development or bugs fixed etc and end up keeping records in other software that are more designed for bug tracking but also having to keep devtrack "up to date" as that's what the managers use to see how much work you've been doing etc they use it to answer questions such as "where's my budget being spent", "is the work being completed by certain dates"
the tool is definitely geared at managers who can generate reports on hours and dates etc
What has been your experience with the version control integration available with DevTrack (VersionLink)? And with which SCM tool are you currently integrated? Thanks!
We're using DevTrack company-wide - a choice made some 2 years ago and before I joined the company. Having past experience with Mantis, Track and Jira, I'm deeply in pain using this tool. It takes a lot of work to perform basic tasks, like adding comments or submitting new issues. There's also no way for me to "watch" a ticket, that is receive notification of changes made to it, unless I owned it at some point. It uses JavaScript to trigger functions and you can't copy the URL of any ticket page. We need to exchange ticket numbers and look them up each time.
It is powerful and highly configurable, but I wish they worked more on usability.
If you do have a choice, stay away from DevTrack and go for FogBugz or Jira instead.