There's a major problem with completely ignoring and not tracking ignored bugs:
They can come back and bite you. What may seem innocuous in one system now may end up being a huge roadblock later on down the line when you want to extend/modify/update said system with new features. While I understand that some bugs are simply too minor and the edge cases simply too rare to bother fixing, it's still a good idea to track them.
This also makes certain that they aren't brought up again as a new bug six months down the line - you can point to the tracking software and say, "Yes. We know about it, and it's not worth fixing."
What may seem innocuous in one system now may end up being a huge roadblock later on down the line when you want to extend/modify/update said system with new features
It may, that's true. But it's very unlikely, and what seems like a huge roadblock now in terms of missing functionality is much more likely to be a huge roadblock later as well.
I think the point of this system is not to say that low-priority bugs are pointless - just that there's almost always going to be something higher priority, so they're not worth the tracking overhead.
Then you fix them later, when it becomes a roadblock. At that point, you'll have much more information about why it's a roadblock and how you should change things so that further development proceeds smoothly. And many bugs may never become roadblocks at all (or may be obsoleted by other changes), so you save all the development effort of fixing things speculatively.
I've seen a lot of time wasted trying to anticipate what might break later on and bullet-proofing that, when the bullet-proofing simply breaks in new and unforeseeable ways when you actually do try to extend it.
As for running across the same bug six months later - at that point, you probably should reevaluate and decide again whether you want to fix it. The "WONTFIX" designation was made on the basis of information that's now 6 months out of date - the fact that the bug has come up to bite you again is perhaps a good reason why now it should be fixed.
They can come back and bite you. What may seem innocuous in one system now may end up being a huge roadblock later on down the line when you want to extend/modify/update said system with new features. While I understand that some bugs are simply too minor and the edge cases simply too rare to bother fixing, it's still a good idea to track them.
This also makes certain that they aren't brought up again as a new bug six months down the line - you can point to the tracking software and say, "Yes. We know about it, and it's not worth fixing."