Bug 1284626

Summary:	Fields in configure will not drag to expand.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ulhas Surse <usurse>
Component:	ovirt-engine	Assignee:	Alexander Wels <awels>
Status:	CLOSED ERRATA	QA Contact:	Petr Matyáš <pmatyas>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.5.5	CC:	awels, lsurette, mgoldboi, rbalakri, Rhev-m-bugs, yeylon, ykaul, ylavi
Target Milestone:	ovirt-3.6.2
Target Release:	3.6.2
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	With this release, users can click and drag to expand the width of columns in the Configure dialog box.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-09 21:14:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	UX	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ulhas Surse 2015-11-23 17:04:12 UTC

Description of problem:
Within configure show Administrator Roles or System Permissions, cannot expand name or user field.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization 3.5.5

How reproducible:
Always

Steps to Reproduce:
1. configure --> Roles --> click on radio button Administrator Roles 
2. Try to make the "name" field longer ( expand )


Actual results:
The fields should show complete name by expanding (drag to expand)

Expected results:
The fields should drag to expand.

Additional info:

Comment 1 Einav Cohen 2015-11-25 14:37:46 UTC

@Alexander - can we easily make the columns in the Roles grid (within the Configure dialog) resizeable?

Comment 2 Alexander Wels 2015-11-25 20:08:14 UTC

Yes, and to head off can we sort questions, added that too.

Comment 4 Petr Matyáš 2016-01-05 11:59:16 UTC

Verified on 3.6.2-3

Comment 5 Alexander Wels 2016-01-19 15:40:50 UTC

Yaniv or Moran,

Can I get pm ack on this?

Comment 7 errata-xmlrpc 2016-03-09 21:14:57 UTC

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://rhn.redhat.com/errata/RHEA-2016-0376.html