A bug is a bug is a bug

“Ladies and gentlemen, due to the usual disturbances, our train will be delayed.”

That was announced on my way to a surprisingly interesting certification training. So what is the point about this? Something was apparently wrong with the track for some time. And it has become the status quo for the engineer. It’s not nice, but he can still do his job, getting people from A to B that is. So what about the passengers then? Most are probably using the train, and thus the track, for the first time or at least not too regularly. For them it might have heavy implications, not being there in time for a connecting train or flight maybe.
This little story relates nicely to a phenomenon I observe in testing from time to time. You come across a bug, report it maybe, but since it’s not that severe, you are not really after it. And after some time you are so used to it, that you don’t bother about it anymore. I strongly suggest you skip that behavior. A bug is a bug and stays one even if it’s been in the software for some time.