BZ 1172390 introduces table header context menu that allows users to control visibility and position of individual columns for all main & sub tabs. https://imgur.com/5dfh8QA This RFE completes the feature by persisting above mentioned column settings in browser's local storage, similar to persisting other client-side settings. Implementing this RFE is non-trivial due to interference with existing column width persistence mechanism (which uses column index).
Vojtech - how much work is left to complete this? Will we be able to push that in 4.0?
(In reply to Oved Ourfali from comment #1) > Vojtech - how much work is left to complete this? The "column control menu" is already implemented, its code is further improved by patch https://gerrit.ovirt.org/#/c/54186/ which also addresses RFE BZ#1285499 to utilize drag'n'drop behavior. Given that RFE BZ#1285499 already has a fix, this RFE is the only one to fix in order to consider "column control menu" UI feature as complete. ETA 3-4 days, just need to ensure that existing "persist column widths" mechanism works well with ability to re-arrange column positions. > Will we be able to push that in 4.0? Yes, I believe so.
Verified in ovirt-engine-4.2.0.2-0.1.el7.noarch ovirt-engine-webadmin-portal-4.2.0.2-0.1.el7.noarch The visibility, position and width of individual columns are persistent across sessions or page reloads. The settings are stored in browser's local storage.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1488
BZ<2>Jira Resync