1. General
  2. Ideas
+9
Under review

resolution options e.g. fixed defered, not a bug

Ian Barrow 9 years ago • updated by tech 8 years ago • 5
I love the "Not a bug" used in this knowledge base. that is associated to the resolution of the bug.

Would be really good if we could also have that in damn bugs.
If it's already there my apologies.
resoultion could be something like the following:

Fixed
duplicate
not a bug
defered

What do you think?
Charles Wood 9 years ago
Also "Can't/Won't Fix".
Under review
tech 9 years ago
QATester1 8 years ago

Please implement this. We need to document why the bug has been closed. Lean Testing does not provide this dimension. e.g Closed (Wont Fix) Closed (Fixed) etc.

Charles Wood 8 years ago

Bug statuses can now be customized. I created several "Closed" statuses like "Not A Bug", "Won't Fix", etc.

tech 8 years ago

There are two reasons why we didn't do this by default:


1) It's easy to get lost if there's too many different statuses. When a project manager wants to know the status of his project, it's better if he doesn't have 15 different statuses to look at.


2) Say we added another, specific field called "reason" if the status is "closed". You might say it takes 10 seconds to fill it in, but 10 seconds times 1000 bugs a year adds up quickly.


I personally don't feel the value added is significant enough to justify this time.


However, I know I'm not always right and this might be super important for some users. We'll get to it, I just don't know when.


Thanks,


Simon


Customer support service by UserEcho