Duplicate of bug links to $current_package/$bug_number

On 3/22/06, Paul Sladen <email address hidden> wrote:
> Public bug reported:
> https://launchpad.net/malone/bugs/35945
>
> Affects: malone (upstream)
> Severity: Normal
> Priority: (none set)
> Status: Unconfirmed
>
> Description:
> Going to a URL such as:
>
> https://launchpad.net/distros/ubuntu/+source/discover1-data/+bug/35473
>
> Lists several duplicates on the left-hand-side. Clicking on one of
> these will go to a link such as:
>
> https://launchpad.net/distros/ubuntu/+source/discover1-data/+bug/28262
>
> which asks:
>
> This bug is not recorded as needing to be fixed in the discover1-data
> (Ubuntu) package.
>
> It should probably instead take the user to:
>
> https://launchpad.net/bugs/28262
>
> which is a redirect to the original package that the bug was filed
> against, eg:
>
> https://launchpad.net/distros/ubuntu/+source/xorg/+bug/28262

The main "not recorded as needing to be fixed in..." use case is when,
for example, duplicate bug searches are smart enough to "expose"
similar bugs found in other contexts, while keeping the user in the
current context. This provides an easy to way say that the bug also
occurs in the current context.

But for the duplicate bugs portlet, perhaps it makes sense to link to
the bug in the current context only if the bug is actually reported in
the current context (and I can see why, practically speaking, it might
not be), otherwise to use the /bugs/NNN URL.

mpt, what do you think?

Cheers,

--
Brad Bollenbach

Agreed entirely. :-)