Finding bugs with Unknown status, was Re: Problems linking bug w/ upstream
Bjorn Tillenius
bjorn.tillenius at gmail.com
Fri Nov 10 21:52:52 GMT 2006
On Fri, Nov 10, 2006 at 03:47:01PM -0600, kiko at async.com.br wrote:
> On Fri, Nov 10, 2006 at 11:10:10AM -0500, Jonathan Jesse wrote:
> > > Alas, it's easy to miss:
> > >
> > > https://launchpad.net/products/keep/+launchpad
> > >
> > > I think this should probably be merged with the details page..
> > > --
> > > Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331
> >
> > One further question, I see that if I search on the Product Keep there are
> > no bugs reported, but if I search on the package keep there are bugs. Is
> > there a way to link the two. I apologize if this shouldn't be sent
> > directly to you, but to a mailing list
>
> Interesting. Once you reported it upstream, you should be able to see
> the bug in:
>
> https://launchpad.net/products/keep/+bugs
>
> The reason you don't is that the status is still Unknown until it syncs
> up with the remote tracker. Bjorn, we omit bugs with status Unknown.. do
> you know why? I think we shouldn't omit them.. or perhaps at least not
> if it is Unknown for the context you are currently in. What do you
> think?
I think we omit unintentionally, since it's not consider an open or
closed status. We probably should consider it an open bug.
Regards,
Bjorn
More information about the launchpad-users
mailing list