| Description |
Make it easy:
* remove the and or condtion from the screen
* imply "and" condition on differnt fields and "or" condition on similar fields
I believe we should standardize the search screen - there should be no or condition and no and condition we should imply them.
The logic would work as follows:
1) if you have multiple coditions that filter the same field we would imply an or Filter
2) if you have a different field you would imply an and conditon,
for example:
|User|Status|Severity|
|Adam|open|Blocker|
|Adam|open|Standard|
|Adam|closed|Blocker|
|Greg|open|Standard|
|Greg|open|Blocker|
|Greg|closed|Blocker
|
Logic:
* you would never want an "and" condition on similar fields User = Adam and User = greg - would never return any records because a record cant be greg and adam at the same time
* You would only want or on differnt fields in rare conditions and that would be something you could not ge in our filters - User = Greg or Status=open would give you all gregs calls open or cloded - -- and adams open - while there may be some value of lets make things simple and not account for that in the interface
so -
user = adam
user = greg
status = open
would be interpretd as
(user = greg or user = adam) and status = open
and give the following results
|User|Status|Severity|
|Adam|open|Blocker|
|Adam|open|Standard|
|Greg|open|Standard|
|Greg|open|Blocker|
user = adam
status=closed
status = open
would be interpretd as
(status = open or status = closed) and user=adam
and give the following results
|User|Status|Severity|
|Adam|open|Blocker|
|Adam|open|Standard|
|Greg|open|Standard|
|Greg|open|Blocker
|
|