Timeline for How to respond to a customer when their bug can't be reproduced
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 25, 2020 at 8:49 | answer | added | Erdrik Ironrose | timeline score: 3 | |
| Jun 24, 2020 at 19:12 | comment | added | Doc Brown | Ok, not a 100% dupe, but very similar question: Dealing with non-reproducible bugs - just replace "project manager" by "customer" in the question and transfer my answer to your situation. | |
| Jun 24, 2020 at 19:07 | comment | added | Doc Brown | @BenCottrell: if you don't insist to read the question literally, but read it as "How to deal with the situation when a bug can't be reproduced", it becomes a software engineering issue (and how to include a customer into the situation can indeed be part of a solution). However, I guess this is a duplicate, I may have answered something similar some years ago. | |
| Jun 24, 2020 at 17:54 | vote | accept | Stein Christensen | ||
| Jun 24, 2020 at 17:52 | answer | added | Karl Bielefeldt | timeline score: 11 | |
| Jun 24, 2020 at 17:37 | review | Close votes | |||
| Jun 30, 2020 at 3:04 | |||||
| Jun 24, 2020 at 17:21 | comment | added | Ben Cottrell | This question really has nothing to do with software engineering, it's a customer service issue. The decision on how to respond and what to do next is a business one, so you need take this up with whoever at your organisation is responsible for decisions related to customer service or product management. | |
| Jun 24, 2020 at 17:05 | review | First posts | |||
| Jul 8, 2020 at 17:06 | |||||
| Jun 24, 2020 at 16:58 | history | asked | Stein Christensen | CC BY-SA 4.0 |