This post originated from an RSS feed registered with Java Buzz
by Michael Cote.
Original Post: "That's a request, not a bug."
Feed Title: Cote's Weblog: Coding, Austin, etc.
Feed URL: https://cote.io/feed/
Feed Description: Using Java to get to the ideal state.
Don't confuse an omission in the requirements/user stories/backlog a bug once the code has been written, and you find out the code doesn't do what you want. It certainly is a "bug" in the product owner phase of the project, but once code has been written "to spec," it becomes a feature request if you want it added in.
Of course, that kind of passing the buck, division of labor is what drives everyone crazy and causes customers to say, "WTF, dude, I just want it to work."