Bug searches should be case-insensitive with respect to status values

[Brad Crittenden]

Searches should not be case-sensitive with respect to the values passed as importance, status, etc.

The following search generates an OOPS because we use 'critical' instead of 'Critical':

https://bugs.edge.launchpad.net/ubuntu/+bugs?search=Search&field.importance=critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed
For the feeds project we'd like to normalize the query string for caching performance. To do that we sort the query string and would like to use a normalized case by converting the entire query string to lower case. Currently that is not possible.

[Curtis Hovey (sinzui)]

lazr.enum handles title and token, but not cases-insensitivity. So while it is backwards compatible, it is not forward looking. I think Item and DBItem need revision to make our URLs lowercase.

[Francis J. Lacoste (flacoste)]

Do bug searches uses the DBItem infrastructure? I though there was some URL mangling done for bug search to support old status names. I'm adding a task to launchpad to represent the lazr infrastructure needed for this.

[Robert Collins (lifeless)]

Any reason that lazr can't do case-insensitive matches on enums?

[Robert Collins (lifeless)]

(high, as per zero-oops-policy)

[Gary Poster (gary)]

I think that doing a case insensitive match ought to be fine. We appear to be guaranteeing uniqueness in a case insensitive way already, if I read the code correctly.

[Jonathan Lange (jml)]

The lazr.enum part of this is marked as In Progress, but the branch is merged. What needs to happen to fix it?