project name picker search / vocabulary is hard/impossible to use (too many results on exact searches)

I don't think this is really a regression. I get why it could be tagged as that. But the bug is nearly two years old now. I doubt many people remember life before the pickers now. :-) I'm guessing that is what made the bug critical, and I also don't think it's a critical issue either.

I don't mean to say this isn't serious. It is. And it's a serious wart on Launchpad. But it also requires feature level work to fix, and there is a work around for this issue, too.

Since a squad is working on the disclosure story now and the bug is arguably not a regression, I will downgrade this to HIGH.

Robert and I chatted for a long while on IRC about this. "requires feature level work" was a bad statement. ignore that bit.

I'm mostly arguing that this isn't a regression *and* it isn't critical. How this plays in our current policy, I don't know. But I feel we need some tweaks to the policy if this sort of bug can be labeled critical. I'd argue that web app "regression" is harder to spot than "oops" or "timeout" and probably shouldn't get a default critical status. But I can take those concerns somewhere other than this bug. :-)

Cheers,
deryck

On Tue, May 24, 2011 at 10:34 PM, Deryck Hodge
<email address hidden> wrote:
> I'm mostly arguing that this isn't a regression *and* it isn't critical.

For 'normal' users this bug might mean that they can't file a bug
because they can't select the right project.

Olaf

On Tue, May 24, 2011 at 4:43 PM, Olaf van der Spek <email address hidden> wrote:
> On Tue, May 24, 2011 at 10:34 PM, Deryck Hodge
> <email address hidden> wrote:
>> I'm mostly arguing that this isn't a regression *and* it isn't critical.
>
> For 'normal' users this bug might mean that they can't file a bug
> because they can't select the right project.

That is precisely right.

-jay

Actually, after investigation, it is not regression. We never removed the old way of reassigning a project / changing a status on the bug task row (to keep the possibility of adding a comment at the same time than changing status.)

@Olaf and @Jay: You don't select the project when filing a bug, you are already on the project.

Just to be clear, this is an important bug and we are working on it. But it's not a regression and doesn't match our Critical criteria.

On Thu, May 26, 2011 at 12:06 PM, Francis J. Lacoste
<email address hidden> wrote:
> Actually, after investigation, it is not regression. We never removed
> the old way of reassigning a project / changing a status on the bug task
> row (to keep the possibility of adding a comment at the same time than
> changing status.)
>
> @Olaf and @Jay: You don't select the project when filing a bug, you are
> already on the project.

I didn't say I was filing a new bug. The problem is when you have a
bug that you need to reassign to Launchpad. The project selector won't
allow you to select to move the bug to Launchpad because too many
results are returned for the selector.

> Just to be clear, this is an important bug and we are working on it. But
> it's not a regression and doesn't match our Critical criteria.

I'm not arguing about High vs. Critical :) I'll leave that up to you
guys to determine ;)

-jay