Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When does a non-critical bug become a feature or should a bug always remain as a bug?
For example. Should there be a statute of limitations in place.
For example, if you have a defined statute of 1 year. The bug was introduced over 18 months ago, but only noticed today.
Should that bug be defined as “this is now how the system works” and to change it, it should be placed on the backlog for prioritisation.
A “bug” is normally seen as an impediment to some execution, generally by creating a unworkable situation. Outside of that, a different way of successfully executing can only be labelled a bug when it does not conform to a given specification. If it becomes acceptable, then the specification changed and therefore the bug does not exist anymore.