Closed Bug 27552 Opened 26 years ago Closed 22 years ago

Keywords in advanced query are case-sensitive.

Categories

(Bugzilla :: Query/Bug List, defect, P4)

2.13

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: CodeMachine, Assigned: endico)

Details

I'm probably triggering a Jihad here, but I noticed that keywords are case sensitive, ie if I type DONTTEST or whatever, it won't get converted to donttest. I don't see any reason for this to occur and any instance of two keywords that are case-insenstive equal is going to confuse people. Sure, at the moment they get told the keyword doesn't exist, and we don't have case-insensitive equal keywords, but I don't see this as optimal. At the very least, if a keyword isn't found, a case-insensitive search should occur and say "Unknown keyword named XYZ. Perhaps you meant xyz, XYz or Xyz?", along with links to process_bug again, and where the suggestions are real keywords.
tara@tequilarista.org is the new owner of Bugzilla and Bonsai. (For details, see my posting in netscape.public.mozilla.webtools, news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara
The last paragraph of my last comment has been generalise into bug #18054.
Err, wrong bug, generalised into bug #35924.
Note: Need to verify this with both simple and advanced querying.
Adding default QA contact to all open Webtools/Bugzilla bugs lacking one. Sorry for the spam.
QA Contact: matty
According to Bonsai this was fixed on 07/13/2000 by Terry. It seems to all work except advanced querying. Dawn, could you please look at this at the same time as bug #45224.
Target Milestone: --- → Bugzilla 2.16
Summary: Keywords are case-sensitive. → Keywords in advanced query are case-sensitive.
Priority: P3 → P4
Mass moving to new product Bugzilla...
Assignee: tara → endico
Component: Bugzilla → Query/Bug List
Product: Webtools → Bugzilla
Version: other → 2.13
No reason keywords should be case-sensitive - no-one would want both BiggerMan and BigGerman keywords. However, this is an RFE without a patch; -> 2.18 ;-) Gerv
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
This is a bug, only advanced query is sensitive.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
i dont know when v2.18 is expected but the last comment was posted months ago (2001-11-17 18:22) comment #8 is spot on, hits the nail right on the head ... I would really like if bugzilla automatically corrected the case needed for the keywords (it would be even better if it could compensate for my lousey speling but that is another issue entirelY).
Severity: normal → minor
OK, I just tested this on the Tip (2.17.6) and read the code and it all works. Searches by keyword are case-insensitive unless you use the boolean charts and choose one of the match options that explicitly specifies case-sensitive. Also, process_bug does permit the keywords to be specified in either case while show_bug shows it using the same case as the admin specified. editkeywords.cgi will not permit 2 ketwords to differ in case only. This WORKSFORME
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
clearing target on worksforme/duplicate/invalid so they'll show up as untriaged if they get reopened
Target Milestone: Bugzilla 2.18 → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.