Make it possible to setup the dup-searcher to search other projects.

The key here is to be able to tell the dupefinder that $project is related in some way to $project_set, so that the dupefinder then searches on those project too.

I think what might be really cool would be implementing this without adding any extra interface. Instead of requiring QA people to realize the common misfiling and link the projects/packages themselves, Launchpad could set up the duplicate-finding link from X to Y automatically whenever more than N% of bug reports filed under X get marked as duplicates of bug reports filed under Y. (You'd need to wait until X had a decent number of bug reports, 200 or so, so that a random blip didn't send the proportion over the threshold.)

Non-rhetorical question: Do we have stats on how often that happens? (I.e., pairings between project X and Y where bugs filed in one often turn out to be dups in the other?)

2010/1/11 Karl Fogel <email address hidden>:
> Non-rhetorical question: Do we have stats on how often that happens?
> (I.e., pairings between project X and Y where bugs filed in one often
> turn out to be dups in the other?)

No, unfortunately, just anecdotal evidence (for example, we still - I
think - get a lot of Ubuntu bugs filed on Launchpad itself).

Graham Binns <email address hidden> writes:
>2010/1/11 Karl Fogel <email address hidden>:
>> Non-rhetorical question: Do we have stats on how often that happens?
>> (I.e., pairings between project X and Y where bugs filed in one often
>> turn out to be dups in the other?)
>
>No, unfortunately, just anecdotal evidence (for example, we still - I
>think - get a lot of Ubuntu bugs filed on Launchpad itself).

Okay. This would be a useful thing to get stats on -- that is, if we're
talking about guiding UI implementation based on it, we should know
those stats first I think.