Here's one appropriate response when somebody requests a change to a program:
"A bug? What do you mean, a bug? That's not a bug; that's an undocumented feature. Now go away and stop bothering me." (Turn away, mutter to self.)
Here's another appropriate response:
"A broken test, you say? Aye, aye, sir, ma'm; yes, yes, YES! I'm all over it, right away!"
The moral? A bug is not a bug until you have a broken test to prove it. If you don't like the behavior of your program, create a broken test. Then (and only then) are you allowed to change the behavior, by fixing the test.
And if fixing the test didn't result in the desired behavior, you had the wrong test to begin with.