[Greg McKaskle]

This totally depends on your style of working, but we tend to have a status field -- bug reports tend to come in waves, and the programmer can't keep up. Status helps communicate to the team what should have been fixed already --report again if it still happens for you, but these aren't supposed to be fixed, so update their description if necessary, but don't file another bug report. This may have been what you were using category for.

Also, some bugs are more severe than others, we we tend to have a severity or impact field. This better allows the programmer to determine the priority for fixes (if you are only able to fix a few ...).

These and any other fields are less important if you have good communication, and more important if the person isn't right in front of you.

Greg McKaskle