Linking package to bug report doesn't suggest checking upstream
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
When you record a bug as affecting a particular distribution package, the usual next step is to check whether the bug also occurs upstream. Perhaps Launchpad should suggest this explicitly.
Where Launchpad knows the upstream project, it could suggest something like: "Next: Have you tried reproducing the bug using upstream <project name>?"
Where Launchpad does not know the upstream project, it could suggest something like: "Next: Is the upstream project for <package name> registered in Launchpad?" with links to register the project or link it to the package.
It might be best to display these suggestions only to QA people, so as not to daunt bug reporters.
Doing this well would require first fixing bug 76416, so that Launchpad does not uselessly encourage people to link (for example) Ubiquity or Apport bug reports to upstream projects.
description: | updated |
tags: | added: ubuntu-upstream-relations ui |
Changed in malone: | |
status: | New → Triaged |
tags: | added: bugwatch |
Changed in malone: | |
importance: | Undecided → High |
tags: | added: story-bug-q-and-a |
tags: | added: better-forwarding |
tags: | added: feature |
well the 2nd step should definitely be shown to common-users.
When I suggested this idea on the ML it was more on the side of letting reporters know or have a brief idea of how much the package against the bug is being filled gets more or less (or none) attention from devs.
I guess that would be a new wish bug?