Making duplicate bug detection and consolidation easier
With automated bug reporting from apport, kerneloops and checkbox(?) we frequently have duplicate bug reports submitted. The duplicate bug reports usually don't provide much value, subsequently patterns should be written to prevent filing of duplicates. There should also be facilities for identifying which bugs would most benefit from a pattern. Additionally, tools for finding and consolidating duplicates already reported should be developed and deployed.
Blueprint information
- Status:
- Complete
- Approver:
- Marjo F. Mercado
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Brian Murray
- Definition:
- Approved
- Series goal:
- Accepted for lucid
- Implementation:
-
Implemented
- Milestone target:
-
lucid-alpha-3
- Started by
- Marjo F. Mercado
- Completed by
- Brian Murray
Whiteboard
Work items:
[brian-murray] Check with ubuntu-bugcontrol to confirm that bug subscription for pattern writing is okay: DONE
[pitti] Update apport-retracer to subscribe ubuntu-bugcontrol to crashes with more than 10 duplicates (bug 487900): DONE
[brian-murray] Find out and document process for getting translator help with bugs: DONE
[brian-murray] Notify bugsquad / triagers about apport symptoms and particulary the one for storage devices in karmic: DONE
[brian-murray] Write a launchpadlib script utilizing searchTasks.
[brian-murray] Update bughugger to make working with duplicates easier: DONE
[brian-murray] Work with Launchpad bugs team to ensure bugs being marked as a duplicate does NOT send an e-mail to subscribers of the master bug report (bug 418659): DONE
[brian-murray] Update apport to strongly encourage people to report a new bug instead of using apport-collect with a bug that is not theirs: DONE
[pitti] Update the list of files that apport searches (bug 444975): DONE
[brian-murray] document how to write a bug pattern better for the Ubuntu Bug Control team (and developers) and notify: DONE
