Bug 724790 (BRMS-629) - Toggle button for selecting visible columns in asset lists should also be able to hide the column selection panel
Summary: Toggle button for selecting visible columns in asset lists should also be abl...
Keywords:
Status: VERIFIED
Alias: BRMS-629
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: BRMS 5.2.0-Dev1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: BRMS 5.3.0.GA
Assignee: manstis
QA Contact: Jiri Locker
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-12 13:08 UTC by Jiri Locker
Modified: 2014-10-27 01:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The toggle button for selecting visible columns in the asset lists did not hide the column selection panel when pressed after making a selection.
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-629 0 None Closed Toggle button for selecting visible columns in asset lists should also be able to hide the column selection panel 2012-06-26 14:25:38 UTC

Description Jiri Locker 2011-07-12 13:08:23 UTC 
securitylevel_name: Public

See GUVNOR-1482.
Comment 1 Jiri Locker 2011-07-12 13:09:18 UTC 
Link: Added: This issue depends GUVNOR-1482
Comment 2 manstis 2011-10-18 11:03:39 UTC 
This was fixed for GUVNOR-1482
Comment 3 Jiri Locker 2011-11-25 14:31:49 UTC 
Fix verified in BRMS 5.3.0.DEV5.
Comment 5 lcarlon 2012-05-03 01:09:49 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The toggle button for selecting visible columns in the asset lists did not hide the column selection panel when pressed after making a selection.
Note You need to log in before you can comment on or make changes to this bug.