Bug 721053 - Delete All and Acknowledge All buttons on Recent Alerts portlet delete/acknowledge *all* alerts, not just the 5 most recent alerts displayed by the portlet
Summary: Delete All and Acknowledge All buttons on Recent Alerts portlet delete/acknow...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: rhq41 rhq41-ui
TreeView+ depends on / blocked
 
Reported: 2011-07-13 15:34 UTC by Ian Springer
Modified: 2013-08-06 00:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:20:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Ian Springer 2011-07-13 15:34:13 UTC
This isn't intuitive. A user could easily accidentally delete or acknowledge all alerts in the system, when they only intended to delete or acknowledge the alerts shown by the portlet.

Comment 1 John Mazzitelli 2011-08-16 17:44:41 UTC
to easily solve this, we should hide the "all" buttons (delete all, acknowledge all). It is easy enough for the user to select the small number of rows shown here (typically only 5) and do a "delete" or "acknowledge". Otherwise, I think we would have to hack up some of the datasource code.

Comment 2 John Mazzitelli 2011-08-17 20:17:04 UTC
master commit 1a38866

the alert portlets no longer show the delete all and ack all buttons, so this problem goes away. This isn't too bad because the portlets are small anyway, and these two extra buttons with the long labels crowd the button area on the portlets and sometimes clip.

Do delete all or acknowledge all in the portlets, you just shift-click the first and last or you just control-click all of them. 

the normal alert history view still has the ability to delete all and ack all

Comment 3 Mike Foley 2011-08-18 14:03:41 UTC
verified 08/18 build

Comment 4 Mike Foley 2012-02-07 19:20:04 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


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