Skip to main content

How to avoid duplicated bug reports, described from different user perspective  ?

We get a lot of bug reports that ends up as the same bug, but are described through the eyes of a different user. 

For example one can see a device has crashed, the other sees communications loss and the third will see that she can't install a driver for the device. I

I was thinking of ways to solve this, my main idea was adding some kind of tags to the bug when the root cause is found, the tags should include other possible features, or phenomenons related to it. This

This is far from perfect, and the greatest drawback is that each tag will quickly have many bugs attached to it, making association by someone not familiar with the root cause impossible, using the example above aa crash will be related to endless bugs.

How to avoid duplicated bug reports, described from different user perspective  ?

We get a lot of bug reports that ends up as the same bug, but described through the eyes of a different user. For example one can see a device has crashed, the other sees communications loss and the third will see that she can't install a driver for the device. I was thinking of ways to solve this, my main idea was adding some kind of tags to the bug when the root cause is found, the tags should include other possible features, or phenomenons related to it. This is far from perfect, and the greatest drawback is that each tag will quickly have many bugs attached to it, making association by someone not familiar with the root cause impossible, using the example above a crash will be related to endless bugs.

How to avoid duplicated bug reports, described from different user perspective?

We get a lot of bug reports that ends up as the same bug, but are described through the eyes of a different user. 

For example one can see a device has crashed, the other sees communications loss and the third will see that she can't install a driver for the device.

I was thinking of ways to solve this, my main idea was adding some kind of tags to the bug when the root cause is found, the tags should include other possible features, or phenomenons related to it.

This is far from perfect, and the greatest drawback is that each tag will quickly have many bugs attached to it, making association by someone not familiar with the root cause impossible, using the example above a crash will be related to endless bugs.

Tweeted twitter.com/#!/StackSQA/status/73374067398418432
Source Link
Rsf
  • 7.1k
  • 1
  • 24
  • 37

How to avoid duplicated bug reports, described from different user perspective ?

We get a lot of bug reports that ends up as the same bug, but described through the eyes of a different user. For example one can see a device has crashed, the other sees communications loss and the third will see that she can't install a driver for the device. I was thinking of ways to solve this, my main idea was adding some kind of tags to the bug when the root cause is found, the tags should include other possible features, or phenomenons related to it. This is far from perfect, and the greatest drawback is that each tag will quickly have many bugs attached to it, making association by someone not familiar with the root cause impossible, using the example above a crash will be related to endless bugs.