Projects/package owners should be able to require arbitary information in bug reports
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The bug reporting guidelines can be useful but are easy to (dis)miss, potentially causing extra work for bug triagers.
During the UDS-L user interviews Bryce, in particular, said that he lost quite a bit of time in having to chase bug reporters for additional information. A sizeable proportion of bugs went invalid because the reporter never replied to requests for additional info.
In the case of X related bug reports, Bryce needs to know the video driver the bug reporter is using and an X.org log file is useful.
If Bryce could ask Launchpad to insist that the bug reporter at least state their video driver, triage would be quicker and there'd be a greater chance of helping the reporter. Clearly a "I don't know", or similar, option might be necessary.
| Deryck Hodge (deryck) wrote | #1 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: story-bug-q-and-a |
This could likely become higher priority when we get to doing the Bug Q&A feature discussed at UDS-L. There was talk between Tom, Martin. A., and I about having some form of structured data for reporting requirements or even custom fields per project added to the bug Q&A work flow, which would allow for this.