Closed
Bug 45224
Opened 25 years ago
Closed 20 years ago
Advanced keyword query issue.
Categories
(Bugzilla :: Query/Bug List, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: CodeMachine, Assigned: bugreport)
References
()
Details
I wanted to find out what bugs have keywords, so I did an advanced query on "Keywords not equal to <BLANK>". However it brought up too many. So, I then tried the URL above. It's doing something wrong, the list should always be empty!
Reporter | ||
Comment 1•25 years ago
|
||
I thought about trying it a different way, and keyword regexps are accepted but the text has to be made of valid keywords!?
Reporter | ||
Comment 2•25 years ago
|
||
And substrings too. Argh!
Reporter | ||
Comment 3•25 years ago
|
||
Also, the search is order sensitive, and doesn't allow "a b" to refer to multiple keywords, but rather requires "a, b" format. Both of these can probably be handled by canonicalisation.
Reporter | ||
Comment 4•24 years ago
|
||
Dawn, this is similar to the dep query issue. If you can get cc and deps to query properly, you should extend it to keywords. I figure this is caused because keywords are converted to a redundant string on the bugs table and that's why this is happening. If you use the keywords table instead all these problems should go away.
Reporter | ||
Comment 5•24 years ago
|
||
That last comment was primarily about the ordering issues. I'm not sure about the first issue I reported, although I suspect it's the same problem.
Reporter | ||
Updated•24 years ago
|
Whiteboard: 2.14
Updated•24 years ago
|
Whiteboard: 2.14 → 2.16
Comment 7•23 years ago
|
||
Mass moving to new product Bugzilla...
Assignee: tara → endico
Component: Bugzilla → Query/Bug List
Product: Webtools → Bugzilla
Version: other → 2.13
Comment 8•23 years ago
|
||
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
Updated•21 years ago
|
Assignee: endico → nobody
Assignee | ||
Comment 9•21 years ago
|
||
nobody@bugzilla.org cares about these poor bugs and they haven't been touched in nearly 2 months. No way they'll hit 2.18 unless something changes. --> 2.20 If someone adopts them, they can pull them back in.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Updated•20 years ago
|
Whiteboard: 2.16
Assignee | ||
Updated•20 years ago
|
Assignee: nobody → bugreport
Assignee | ||
Comment 10•20 years ago
|
||
You can do this with the negation feature now.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Comment 11•20 years ago
|
||
clearing target of DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as untriaged if they get reopened.
Target Milestone: Bugzilla 2.20 → ---
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•