Linking package to bug report doesn't suggest checking upstream

Bug #182830 reported by Matthew Paul Thomas on 2008-01-14
Affects Status Importance Assigned to Milestone
Launchpad itself

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

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?

Matthew Paul Thomas (mpt) wrote :

That's bug 37926.

Curtis Hovey (sinzui) on 2010-01-22
tags: added: ubuntu-upstream-relations ui
Changed in malone:
status: New → Triaged
tags: added: bugwatch
Changed in malone:
importance: Undecided → High
Deryck Hodge (deryck) on 2010-01-22
tags: added: story-bug-q-and-a
Bryce Harrington (bryce) on 2010-06-23
tags: added: better-forwarding
tags: added: feature
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints