Bug 1003935

Summary: [RFE] Support persistent setting of columns on System search page for user
Product: [Retired] Beaker Reporter: Petr Holasek <pholasek>
Component: web UIAssignee: beaker-dev-list
Status: CLOSED NOTABUG QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.14CC: aigao, asaha, dcallagh, dhoward, llim, pholasek, qwan, rmancy
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-19 08:27:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Petr Holasek 2013-09-03 14:29:46 UTC
Hello,

I'd would be nice to have set of Result columns of Systems search saved for currently logged user. My use case is that I need to set every time System/LoanedTo and System/Owner when want to see if system is really "available".

Comment 2 Raymond Mancy 2013-09-03 22:51:08 UTC
The "Available" sub menu item in the "Systems" menu really should be only showing systems that are actually available to you to use (not necessarily immediately available, but potentially so).

If you would like to repeat your previous custom result columns search, just make sure you're in the advanced search (by hitting 'Toggle Search'), and it should have kept a record of what your previously selected custom result columns were).

Comment 3 Raymond Mancy 2013-09-19 07:07:56 UTC
Petr, can you confirm that this doesn't work for you? What browser are you using?

The system search page uses cookies to store the currently selected Result columns, so when you return to that page they should still be there.

Comment 4 Petr Holasek 2013-09-19 07:47:07 UTC
When I am logged in Beaker in recent FF, it works as you described - so it is fixed. Previously I've used a bit outdated FF 4.x on RHEL6.2, so it is probably the reason.

Thank you very much!
Petr

Comment 5 Nick Coghlan 2013-09-19 08:27:35 UTC
Thanks for checking Petr!