BugTracker.net

BugTracker is an excellent tool for tracking technical changes and issues in a development project - the ability to assign tasks or issues to an individual developer, then assign it back for review and finally closure helps ensure a great quality end result. While it's great for tracking development issues, it's harder to use for content changes and updates, and we've found other approaches to be more effective.

It may not be the best or easiest tool for collecting client feedback during staging and feedback cycles, since the user interface is very developer-driven. Designers, Writers, and Project Managers are able to use it effectively, however.

See above. Recommended questions:

What type of feedback or tracking will we be doing?
Will this need to be client-facing?
How will we track content edits?
How many users will be assigned to issues in a given project?

We are currently using BugTracker.net not only in our Quality Assurance department, but also in our Project Management approach. We use BugTracker.net to keep track of the status of current and historical releases, legacy code as well as constantly using it to track any issues we find in the software. Obviously tracking bugs is the intent of the tool and it does this pretty well.

It is a great Bug Tracking tool when implemented and set up the correct way initially. If you find yourself in the position of having to go through and re name fields on a project level of having to do an overhaul of the user base you will find some frustrations, these are noted in the last question.