Bug 596964

Summary: [RFE] system filtering, same search types should default to or instead of and
Product: [Retired] Beaker Reporter: Jeff Burke <jburke>
Component: web UIAssignee: beaker-dev-list
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 0.5CC: bpeck, mastyk, mcsontos, tools-bugs, xuzhang
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://tinyurl.com/2uwajut
Whiteboard: UX
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-02 12:01:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Burke 2010-05-27 20:16:29 UTC
Description of problem:
 When filtering on the systems page if you are using the same criteria it should default to or not and.

http://tinyurl.com/2uwajut

Comment 1 Raymond Mancy 2010-05-27 21:05:14 UTC
I see what you mean. 
Perhaps though we should have another column which specifies the relationship. 
I can think of instances where we might want the relationship to be and (i.e System/Arch).

Comment 3 Jeff Burke 2011-02-15 13:17:56 UTC
Folks,
 Why was this bz moved out to Future Feature. This is a big flaw with the way searching should work. Can this be discussed further. The examples I gave were
only for the bz this effect many other queries that we use on a day to day bases.
Now that RHTS is gone it is much more overhead to track the same things in Beaker.

Thanks,
Jeff

Comment 5 Raymond Mancy 2011-02-21 23:01:46 UTC
I was thinking about this last night, how you would make this look intuitive.
I like the above example. Perhaps I can try an dmimick that with the and/or option.

Comment 6 Jeff Burke 2011-06-30 14:15:17 UTC
Any progress on this. With so many kernel maintainers now it is a PITA to have so many FF windows open to track the jobs

Comment 7 Raymond Mancy 2012-10-04 10:14:21 UTC
Sorry, no progress has been made towards this. I'd guess that the best chance of getting the kind of functionality you're after is with 860492, although it has not yet been given any target milestone.

Comment 10 Dan Callaghan 2016-04-20 06:41:55 UTC
*** Bug 1328708 has been marked as a duplicate of this bug. ***

Comment 11 Tomas Klohna 🔧 2019-04-01 13:17:58 UTC
Team agreed on implementing option that specifies relationship between values.

Comment 12 Martin Styk 2020-06-02 12:01:20 UTC
Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>