When should a bug go to "Will Not Fix" vs "As Designed" on its final state?



  • Often times we file a bug and later see that it's marked as "As Designed" by the developer. Sometimes it gets marked as "Will Not Fix".

    When a bug is marked "Will Not Fix" then it is supposed to give credit to the tester and an acknowledgement that the bug was valid but it was decided not to fix it.

    What is the thinking process that can be used to decide whether a bug should go to "Will Not Fix" vs "As Designed"?



  • When a bug is marking as "Will not Fix" it may have many probabilities.

    • We need to validate the severity/impact of the bug to the users. If the bug is really valid one but it wont have much impact on the user and business side then it can go in "Will not Fix" category
    • "Will not Fix" innocents the bug will not be fixed in the release instead it can be taken in future releases.

    "As Designed" category will not come under Bug.

    For "As Designed"

    • The functionality of the application is designed in such a way to behave. But the designed functionality can have some issues in terms of usability or business aspects. In such cases check with the module owner or refer the documentation for getting the idea on why it was designed like that.

Log in to reply
 

Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2