extra Status for upstream bugs in overview

[Brad Bollenbach]

On Fri, 2006-21-07 at 19:56 +0200, Thilo Six wrote:
> Hello
> 
> Today i helped a little with bug triage and i came across i little
> problem with the open bugs overview.
> 
> e.g. [1]:
> https://launchpad.net/people/motuscience/+subscribedbugs
> 
> There are two bugs which has been fixed in Ubuntu and wait for upstream fix.
> e.g. [2]:
> https://launchpad.net/products/geda/+bug/44821
> 
> When the bug is open you see the "Fix Released" Ubuntu status but not in
> the overview [1].
> I sugest to have both statuses in overview to better distinguish which
> ones are more important to work on and which ones are allready fixed in
> Ubuntu and "only" wait for upstream.
> Therefor we would need both status in the overview (as like in the open
> bugreport [2]).
> 
> What do think?

A similar issue was reported here:

  https://launchpad.net/bugs/35030

Most, if not all, bug listings show the same bug more than once for bugs
that are reported in more than one package, forwarded upstream, etc.

I see two underlying issues:

1. A bug listing should show only information that the user cares about.
A developer for distro A should never see statuses from distro B leak
into their reports if the user has no interest in distro B. However, if
distro B, or an upstream product, has fixed or rejected the bug, the
distro A developer may want to know that when looking at a listing.

2. To minimize confusion, a bug listing should not list the same bug
more than once, regardless of where the bug's reported.

I don't have a good solution for this problem yet, but here are some
brainstorm ideas to help consider different aspects of the problem in
more detail:

* Allow a bug to have only one status per
distribution/distrorelease/product, rather than being able to track the
assignee, status, milestone, importance, etc. per bug per package. This
makes it easy to not duplicate a bug in a distro or product bug listing
and reduces the likelihood of seeing dupes in +subscribedbugs and such,
and would generally simplify tracking the status of a bug.

* Allow a user to associate themselves with distributions and products
in a user preferences screen. This information could act a magnifying
glass on bug listings, and bug pages, and other parts of Launchpad. So,
if you're associated with distro A, but not distro B, and a bug is
reported in both, you see only the status for distro A in your
+subscribedbugs list. Some exceptions would be made, like being shown
that a "fix exists" if the bug was fixed upstream or by another distro.

* (The most obvious one) Collapse all statuses of a bug into a single
row. mpt would need to be consulted for how best to do this.

Thoughts?

Brad