Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1514899

Summary: [downstream clone - 4.1.9] [RFE] Persist column visibility and position in browser's local storage
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Alexander Wels <awels>
Status: CLOSED WONTFIX QA Contact: Pavel Novotny <pnovotny>
Severity: high Docs Contact:
Priority: medium    
Version: 2.1.0CC: awels, bugs, gchakkar, gklein, gshereme, jspanko, lsurette, lveyde, mgoldboi, pnovotny, rbalakri, Rhev-m-bugs, srevivo, trichard, vszocs, ykaul
Target Milestone: ovirt-4.1.9Keywords: FutureFeature, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: ovirt-engine- Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1285456 Environment:
Last Closed: 2017-11-30 13:07:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1285456    
Bug Blocks:    
Description Flags
screen: column position & data alignment after page reload none

Description rhev-integ 2017-11-19 10:37:21 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1285456 +++

BZ 1172390 introduces table header context menu that allows users to control visibility and position of individual columns for all main & sub tabs.

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).

(Originally by Vojtech Szocs)

Comment 1 rhev-integ 2017-11-19 10:37:30 UTC
Vojtech - how much work is left to complete this?
Will we be able to push that in 4.0?

(Originally by Oved Ourfali)

Comment 3 rhev-integ 2017-11-19 10:37:36 UTC
(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 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.

(Originally by Vojtech Szocs)

Comment 15 Pavel Novotny 2017-11-24 17:22:58 UTC
FailedQA in

The column visibility and width is persistent, but the position persistence is not working correctly.

Go to Disks tab:
1) hide the Alias column
2) change the width of the Status column
3) swap the columns ID and Description.

Reload the page.
1) OK
2) OK
3) not OK: 
   In the table header, the two columns are back in their original positions - not swapped.
   But data in the table have the columns swapped. Also, the data alignment here is distorted.
   See the attached screenshot.

Comment 16 Pavel Novotny 2017-11-24 17:24:06 UTC
Created attachment 1358727 [details]
screen: column position & data alignment after page reload

Comment 17 Oved Ourfali 2017-11-27 13:29:17 UTC
Moving to 4.1.9, although big part of the functionality will land in 4.1.8.

Comment 19 Oved Ourfali 2017-11-30 13:07:17 UTC
This will be fixed only on 4.2.

Comment 20 Tahlia Richardson 2017-12-04 01:18:55 UTC
Clearing doc text based on WONTFIX status.