Bug 826673 - RFE: Add ability to maximize a dashboard portlet
RFE: Add ability to maximize a dashboard portlet
Status: CLOSED CURRENTRELEASE
Product: RHQ Project
Classification: Other
Component: Core UI (Show other bugs)
4.4
All All
high Severity medium (vote)
: ---
: RHQ 4.5.0
Assigned To: Jay Shaughnessy
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-30 14:15 EDT by Jay Shaughnessy
Modified: 2013-09-01 06:00 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-01 06:00:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jay Shaughnessy 2012-05-30 14:15:42 EDT
Dashboard portlets are great for displaying a lot of information in a limited amount of space.  But often you end up scrolling a small window to see all of the data you may be interested in.  Allowing the ability to maximize a portlet would be nice.
Comment 1 Jay Shaughnessy 2012-05-30 14:31:17 EDT
master commit f758dd314f3701432e824cc7509fdba21f76d703
- add this ability
- also, remove sizing controls when in edit more
- also, fix a bug in portlet removal where the portlet window was
  not being fully removed from the current dashboard.



test notes:
try various combinations of minimize/maximize, editMode/viewMode and other header controls.

When minimized the maximize control should go away.
When maximized the minimize and maximize controls should go away.
When maximized the close control should restore (i.e. end maximize)
When maximized the edit mode button should restore (i.e. end maximize)
When in edit mode the minimize and maximize controls should go away.
Comment 2 Heiko W. Rupp 2013-09-01 06:00:32 EDT
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.

Note You need to log in before you can comment on or make changes to this bug.