Non-duplicate bug reports sometimes marked as duplicates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-community |
New
|
Undecided
|
Unassigned |
Bug Description
Bug reports describing similar behavior in similar components are not duplicates. It might make sense to say there's a "bug in Ubuntu caused by this component and that component", then add one component to the report for the other, then mark the non-dual report as duplicate, but it does not make sense to mark a bug in one component as a duplicate of a bug in another component.
Reports that are just kind of about the same thing are not duplicates either. A bug report saying, "I have no option" is not the same thing as one saying, "the default should be something else". A report saying "I can't tell what's going to happen" is not the same thing as one saying, "I want to choose what happens".
summary: |
- Non-duplicate bugs often marked as duplicates + Non-duplicate bugs sometimes marked as duplicates |
summary: |
- Non-duplicate bugs sometimes marked as duplicates + Non-duplicate bug reports sometimes marked as duplicates |
Do you have some examples of where this has happened, perhaps some bug numbers?
We have both automated tools and a bunch of real people who triage bugs, but sometimes they make mistakes. If we can identify where people are making mistakes perhaps there's an opportunity for education?