Comment 4 for bug 35646

On 3/20/06, Björn Tillenius <email address hidden> wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35646
>
> Comment:
> On Mon, Mar 20, 2006 at 10:29:46AM -0000, Dafydd Harries wrote:
> > Sorry, I misunderstood. Indeed, it's confusing that we show existing
> > bugs when you can't file new ones. Short of hiding or deleting bugs for
> > products that don't use Malone, or moving the bugs to Ubuntu, I'm not
> > sure what we can do about it.
>
> Yeah, it's a hard problem to solve. Maybe we shouldn't show bug
> listings of products that don't use Malone. These bugs haven't been
> added been added by filing them directly on the product, they were
> first filed in Ubuntu, and then "forwarded" to the product, which is a
> perfectly valid thing to do.
>
> I think we need to try to explain this in the UI somehow. Hiding the
> bugs isn't a correct thing to do, since it can be good to get a overview
> of all the bugs in product, even if it doesn't use Malone directly. Soon
> we'll start syncing the status of the bugs from the upstream bugtracker.

I agree that a message on the bug listing pages (and bug pages in that
context, perhaps) that explains how these bugs ended up in Malone when
the upstream isn't using Malone is probably a good starting point for
fixing this problem.

Cheers,

--
Brad Bollenbach