When does a bug become a feature request? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 5 years ago.

Improve this question

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 d开发者_运维技巧efined 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.

---

Your question seems to imply that bugs fixes don't get prioritized. I believe that prioritizing should happen somewhat frequently, and that features and bugs should both be treated equally as "issues". Bugs will often be higher-priority than a new feature, but that shouldn't be an automatic decision.

---

I believe that the bug is still a bug no matter when it is discovered in the project lifecycle, and should be defined and documented as such. Remember, documenting a bug does not make it a feature :D

---

Are your developers giving you the "That ain't a bug, it's a feature!" line?

Seriously, a "bug" would be something in the applications that behaved counter to the specifications of the project. Unless the specifications change, I would not expect a bug to ever expire.

---

When you change the specification in response to it.