Timeline for How to deal with bug reports or issues where the reporter no longer cares and no one can reproduce?
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18, 2016 at 18:33 | comment | added | user53141 | If you mark "not reproducible", the reporter may get annoyed if they can reproduce, and reopen it. If you mark "won't fix", and the reporter doesn't care, everyone can just go on with their day. | |
| May 18, 2016 at 16:20 | history | edited | Tomáš Zato | CC BY-SA 3.0 | added 246 characters in body |
| May 18, 2016 at 16:14 | comment | added | gnat | Possible duplicate of How to close a bug that is no longer relevant | |
| May 18, 2016 at 15:19 | comment | added | gnasher729 | @peregrine: You'll never know. Just as you never know about all the bugs that get never reported in the first place. A bug that nobody complains about doesn't seem very important. | |
| May 18, 2016 at 13:59 | vote | accept | Tomáš Zato | ||
| May 18, 2016 at 13:28 | review | Close votes | |||
| May 27, 2016 at 3:01 | |||||
| May 18, 2016 at 13:20 | answer | added | Arseni Mourzenko | timeline score: 2 | |
| May 18, 2016 at 13:15 | answer | added | Robbie Dee | timeline score: 1 | |
| May 18, 2016 at 13:13 | comment | added | Peregrine | If a defect can't be reproduced, how will you ever know if it's really been fixed ? | |
| May 18, 2016 at 13:07 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 | deleted 5 characters in body; edited title |
| May 18, 2016 at 13:04 | comment | added | gbjbaanb | "won't fix" / "no plan to fix" seems more appropriate, though if no-one can reproduce it, mark it as that and close it. Bugs get fixed by subsequent code changes all the time. | |
| May 18, 2016 at 13:04 | answer | added | Bart van Ingen Schenau | timeline score: 2 | |
| May 18, 2016 at 13:03 | comment | added | Ixrec | Everyone's going to use a slightly different term for this, but some variant on the words "no" and "reproduce" will get the point across to pretty much everyone. Where I work we often use the abbreviation "CNR" (can not reproduce). | |
| May 18, 2016 at 12:52 | comment | added | user1666620 | then if nobody cares any more, call it "no longer an issue". | |
| May 18, 2016 at 12:50 | comment | added | Tomáš Zato | The thing here is that it had the unable to reproduce status all along, but as long as the reportee cooperated, the issue could be fixed. Once he decided the problem is not that bad, I am not going to do anything about it of course. | |
| May 18, 2016 at 12:48 | comment | added | user1666620 | "unable to reproduce", "not reproducible" | |
| May 18, 2016 at 12:43 | history | asked | Tomáš Zato | CC BY-SA 3.0 |