"Request fix" misunderstood.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
New
|
Medium
|
Unassigned |
Bug Description
Here's a transcript from an IRC conversation (with irrelevant conversation elided):
< glyph> spiv: So, I tried to request a fix on my screen bug
< glyph> spiv: since apparently nobody is looking at it? The first time it failed, the second time it succeeded - I did nothing different, as far as I can tell
[the failure is OOPS-31D67]
< glyph> Oh
< glyph> I guess the bug is just being ignored then, not that I didn't file it correctly
< glyph> spiv: since none of the options I am presented with made any sense whatsoever, I clicked on "request a fix" hoping that would up the priority somehow :)
The bug in question was https:/
However, there was already a bugtask there for "screen (Ubuntu)", so the "Request fix" attempt failed. A second attempt added a bugtask for simply "Ubuntu".
So, a) the bug reporter isn't confident they correctly used Malone, and b) the "Request fix" links confused them. The relationship between the "Request fix" line and the table above was clearly not obvious to this user.