### Comment:
Is it a bug if it was never in the requirements?  
  
 What I'm saying is that this could be not incompetent coders, but incompetent business analysts who write up the business requirements and not foreseeing this situation. 
  
 Edit: also to add, any change in requirements would be a change request, not usually a bug. Change requests usually take away from stability, while fixing a bug usually enhances stability.

### REPLY:
Absolutely. I would, however, argue that whether it is the fault of the requirements or the fault of the developers any kind of behavior that differs from the intended behavior is still a bug. The people behind the design spec may have embedded that bug into the requirements they built, but it is still a bug.

### END.