Activity log for bug #182830

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.

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.