Editing Software bug (section)

=== Known issue ===
It is common practice to release software with known, low-priority bugs or other issues.  Possible reasons include but are not limited to:

* A deadline must be met and resources are insufficient to fix all bugs by the deadline<ref>{{cite magazine|title=The Next Generation 1996 Lexicon A to Z: Slipstream Release|magazine=[[Next Generation (magazine)|Next Generation]]|issue=15 |date=March 1996|page=41}}</ref>

* The bug is already fixed in an upcoming release, and it is not of high priority

* The changes required to fix the bug are too costly or affect too many other components, requiring a major testing activity

* It may be suspected, or known, that some users are relying on the existing buggy behavior; a proposed fix may introduce a [[wikt:breaking change|breaking change]]

* The problem is in an area that will be obsolete with an upcoming release; fixing it is unnecessary

* "It's not a bug, it's a feature"<ref name=wired>{{cite web|url=https://www.wired.com/story/its-not-a-bug-its-a-feature/|title='It's Not a Bug, It's a Feature.' Trite – or Just Right?|website=wired.com|first=Nicholas |last=Carr|year=2018}}</ref> A misunderstanding exists between expected and actual behavior or [[undocumented feature]]