Avoiding duplicate bug reports

Posted by Jaakko Seppälä on Programmers See other posts from Programmers or by Jaakko Seppälä
Published on 2012-10-19T19:36:14Z Indexed on 2012/10/19 23:20 UTC
Read the original article Hit count: 303

Filed under:

bug-report

I use Linux and other open source software in my home. As I'm not a professional coder, I usually report bugs to developers as my skills are not enough to solve problems on my own.

What kind of things you want me to check before I send a bug report? I mean, once I thought I found a bug in Gedit and I couldn't find similar bug in Bugzilla. But after I sent the report, some developer said that the bug is already in Bugzilla as the bug was in GTK+, not in Gedit. Sometimes it might be hard for an amateur to guess whether some previously known bug would solve the issue I found.

Related posts about bug-report

I have a stacktrace and limit of 250 characters for a bug report

as seen on Programmers - Search for 'Programmers'
I'm developing an xbox indie game and as a last-resort I have a try...catch encompassing everything. At this point if an exception is raised I can get the user to send me a message through the xbox however the limit is 250 characters. How can I get the most value out of my 250 characters? I don't… >>> More
Best practice for marking a bug as resolved in Bugzilla ?

as seen on Programmers - Search for 'Programmers'
I am wondering what is the best way to handle the situation of marking a bug as resolved and providing a version of component/product in which this fix can be found. Context For a project I am working on, we are using Bugzilla for issue tracking, and we have the following: A product "A" with a… >>> More
Is it a bug or a task when something doesn't work, yet, in development process

as seen on Programmers - Search for 'Programmers'
We usually have this dilemma in our team. Sometimes, in order to implement a task or a story we find out that the system must be in a specific state. For example, a specific system configuration has to be made beforehand. The task / story can be completed and it is working as specified on it with… >>> More
Is it good practice to analyse who introduced each bug?

as seen on Programmers - Search for 'Programmers'
I used to analyse performance of programmers in my team by looking at the issues they have closed. Many of the issues are of course bugs. And here another important performance aspect comes - who introduced the bugs. I am wondering, if creating a custom field in the issue tracking system "Blamed"… >>> More
Best practice while marking a bug as resolved with Bugzilla (versioning of product and components)

as seen on Programmers - Search for 'Programmers'
I am wondering what is the best way to handle the situation of marking a bug as resolved and providing a version of component/product in which this fix can be found. Context For a project I am working on, we are using Bugzilla for issue tracking, and we have the following: A product "A" with a… >>> More

Developer IT