Closed
Bug 984814
Opened 12 years ago
Closed 6 years ago
In advanced search, custom search does not allow the insertion of criteria and brackets after criteria have been created
Categories
(Bugzilla :: Query/Bug List, enhancement)
Tracking
()
RESOLVED
FIXED
Bugzilla 6.0
People
(Reporter: mike, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release)
Build ID: 20140212131424
Steps to reproduce:
1. Created a search of form (A AND B AND C) OR (X AND Y AND Z), creating the criteria in left to right order
2. Used and saved search
3. Wanted to create edited variant of search, inserting additional criteria outside (in the SQL brackets sense) the first bracket. That is a search of form:
(D AND E) OR ((A AND B AND C) OR (X AND Y AND Z))
Actual results:
3. Needs to be an 'insert outside' function
Expected results:
3. Could not find way of doing this without re-entering the criteria. Seemed to be no function to insert into first bracket. Checked manual and found no guidance.
Summary: In advanced search, custom search does not allow the insertion of criteria and brackets outside current criteria → In advanced search, custom search does not allow the insertion of criteria and brackets after criteria have been created
I have generalised this slightly as there is a general need to be able to add nesting levels with associated qualifiers and criteria at all points in pre-existing custom searches, and in custom searches that you are in the process of creating. Currently after you have created a clause you can no longer do this.
Comment 2•11 years ago
|
||
This is hugely frustrating when you have complex searches that are slightly wrong in their logic. In thic case you need to start again.
If it is difficult due to the limitations of the GUI, it would be acceptable to turn the search into a string, and let it be edited directly, similar to how MS Access works for GUI queries. The search is already stringified for creating the URI, but that string is too user unfriendly to edit.
Comment 3•6 years ago
|
||
Solved in Bug 1543700.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•