What should be a good BugTracking tool?

Question

I found a lot of questions asking for the best tools, but no one asked for the features you really need ? And what features do you never need?

(I caught myself comparing tools on function matrices. Something I hate, because in the end I will use only 3-4 of the most important functions and leave the rest untouched.)

Answer 1

He must:

• collect errors
• order of errors in priority / severity / term, etc.
• assign errors to developers
• track error history
• bind similar errors together
• customer links
• reference to fixed bugs for release
• provide sufficient information or a link to receive information for reproducing the error
• can be used by more than one developer
• The error status should be available to the client who reported the error.

And there is more.

Answer 2

Easy end-user data entry. Without this, you will not introduce errors, which is equal to a useless error tool.

Answer 3

I cannot answer this question for you, because I cannot predict what is important to you or what your situation is:

• Do you work in a large or small development team, or are you a one-person store?
• Would it be helpful to have a system where you could automatically send your applications to the problem reports that create incidents in your bug tracking software?
• Is it possible to predict the release schedule more importantly, or is it just something for a third-party project that you do in your free time?
• Is integration with a control source important?

In fact, you are the only one who can respond to your functions.

Answer 4

These are 3 required functions that I consider the most important:

• Web interface so people can follow
• Integration with source control, otherwise it is very difficult to track who did what and deploy patches.
• Customizable Email Notification Workflow

Answer 5

Things I really would like to see:

1) Voting - that is, how many customers / users are causing this error?

2) Severity / priority / whatever - the distinction between these terms is subtle and usually (IMHO) insignificant, but you should have some idea of ​​how important the error is. Most tools have this, but complicate it too much.

3) Dependencies - both internal (from other errors in one system) and external (external libraries, software, etc.). Most errors have this in fact, but this is usually not expressed in the database, which leads to lengthy, pointless debate during sorting.

Things that I think are basically meaningless:

1) Any extensive questionnaires - any error tracker that asks too many questions will simply get bad data. This is worse than no one.

2) Controversial, but mandatory daily / weekly / any email notifications. They are simply registered as spam / ignored / filtered out. If developers need to fix bugs and are not a management issue. The software cannot fix this.

Answer 6

It is required:

Email Notification. Status Group notifies Group rights Web interface Easy / fast interface