Unwanted bug reports Martin Jansson

A few months ago I reported a bug to the installer of a security radar at a door. He had placed a radar just inside the door so that people who were going out never had to use their pass card to get out. Instead you just walked up to the door and it opened, that is from the inside going out.
The front door

The front door

The bug that a co-worker found was that you were able to pull open the door a quarter of an inch, just enough to be able to put in a little stick and then wave it infront of the radar. It actually goes quicker to use the stick instead of the card.

I confronted the installer of the security radar and told him about the bug. He answered me “No, that is not possible.”. I told him again, it is so and that one of our consultants use it since he has no pass card. He answered me again “No, that is not possible.”. I did not have time to argue so I left.

I am now going to notify the owner of the house so that they understand the problem. Apparently there are more people using this trick when they have forgotten their card, so the stick is just below the pass card holder for easy access. A few years ago there was something called “Not my job award!”, I guess this would fit into this category.

Pradeep Soundararajan May 4th, 2009

🙂 A rephrase of “No, that is not possible” could be, “I haven’t heard it nor I think it exists for the benefit of myself and someone else in the organization, I care about”.

Martin Jansson May 4th, 2009

I think he did not see me as the customer, who had bought the system. But in fact I was the customer of the customer having the office in that building. So, I guess he was just a bit unproffessional.

Btw, he did not use the exact phrase above… I tried to translate it the best I could from Swedish to English. I tried to bring the essense of what he said, but I could easily have written your statement directly. Considering that he rolled his eyes, looked away from me quite quickly, had a certain tone in his voice etc.

Henrik Emilsson May 4th, 2009

Lovely story! 🙂

I remember that we encountered a similar thing when we were dealing with Compuware and their product QA Director.
One bug we reported (amongst several) was a serious crash that made the application unusable, we could not list the test scripts. We also managed to diagnose the underlying error: Two test scripts had received the same GUID i.e., the test scripts were no longer unique. I am not really sure, but I think that we had some clues on why this had happened (repro steps), but we were afraid of trying out too much on our production system. So we reported this bug to Compuware, including the SQL-scripts that listed the two erroneous test scripts, screenshots and error logs, etc.
After we had penetrated the first and second lines of support we finally got to talk to someone from the development team that, at least in our belief, knew something about the system. His respond was (something like):
“That is impossible. You know two test scripts cannot get the same guid; that would break the application.” (sic!)

Martin Jansson May 4th, 2009

I remember that as well! QA Director brings back lots of nice memories.

If I remember correctly the first line support asked “Did you turn on the power of the computer?” after he/she had read all the repro-steps for the bug.