Question

Possible Duplicate:
What should a good BugTracking tool be capable of?

Although there is a large set of features that a bug tracker can have I feel like it is a little overkill and was considering rolling out my own solution. With that being said I didn’t want to remove any core functionality that might be used frequently with existing solutions.

The ones I can think of so far: – creating bugs – assigning bugs – closing bugs – adding description to the bug

Thanks!

Answer 1

• Communication between the developer and the user.
• Ability for the user to assign certain bits of information such as severity (how much that bug relates to them).
• Ability for the developer to override that priority and, if possible, give a reason.
• Ability to assign tasks to a developer.
• Ability to sort between bug, enhancement, and feature request. The difference between an enhancement and feature request is very subtle but VERY important.
• Ability to attach files (such as screen shots)
• Ability to have custom fields (such as being able to select which OS, which service pack level, application version, etc).
• Ability to have custom user profiles which also give detailed information about their hardware. It’s also nice to be able to have the users phone number (if they are on your LAN) so you can ask questions, if needed.
• Privacy. Some items, such as security exploits or information that deals with financial information, will need to be kept secret. Even OSS does this from time to time until they can get a patch ready. Everyone has their own rules.
• Ability to show the changes between revisions so you can email out a Change Log so users know what you have and have not done.
• Reminders about which items are left undone and are assigned to you / unassigned at all.

That’s all I can think of…