An issue list is a pretty simple concept: when someone reports a bug or other important issue, you want to keep a copy of that report around so you don’t forget it. Pretty straightforward, right? (And since developers often get squeamish when we talk about bugs, we’ll use the blander and more politically correct term issue.)
However, there can be more to keeping track of an issue than just the description of the issue itself. Keeping track of and effectively communicating details about issues can be tricky. You need to know the following:
What version of the product has the issue?
Which customer encountered the issue?
How severe is it?
Was the problem reproduced in-house (and by whom, so they can help you if you’re ...