Wishlist: links to related packages

Bug #217207 reported by era
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Incomplete
Low
Unassigned

Bug Description

When I have found a bug but don't know which package it's in, it would be useful if the "Report a bug" wizard could point me to related packages.

As an example; for me, the live CD complex is problematic. I have learned (the hard way, we might add) what "ubiquity" and "casper" mean but now I found myself wondering again where to file a wish for an additional package to include in the Live CD. Looking at Ubiquity and Casper bugs, I see no bug reports which resemble mine, but I have no idea where to go next.

(I ended up reporting bug #217138 against Casper, hoping that somebody who knows this stuff better will reassign to the right package, unless of course Casper was the right package for this bug after all.)

The "Depends": and "Suggests": fields are -- in this case, at least -- not sufficient for finding related packages. They also by themselves don't include any description of the packages, so for example, if I am not familiar with "dmsetup" (in the Depends: of casper) I will need to look it up separately.

Curtis Hovey (sinzui)
affects: launchpad-foundations → malone
Curtis Hovey (sinzui)
Changed in malone:
status: New → Triaged
importance: Undecided → Low
tags: added: feature
Revision history for this message
Bryce Harrington (bryce) wrote :

I can totally understand the trouble of trying to determine the right package to file a bug against.

However, this bug's description is currently a bit vague as far as how to address this problem. Could you elaborate a bit more on how you envision it should work? Perhaps that would clear things up conceptually.

Changed in malone:
status: Triaged → Incomplete
status: Incomplete → New
Revision history for this message
Bryce Harrington (bryce) wrote :

Perhaps this is basically a dupe of bug #178307 ? Take a look at that one and see if you agree.

Changed in malone:
status: New → Incomplete
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

One possibility would be to use the duplicate finder, or something similar, to return a list of packages that most often appropriately contain bug reports that use the same words as the summary you're entering. (You'd calculate "appropriately" by whether the report was Confirmed, Triaged, or Fix*ed.)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.