Bug 535147 (RHQ-1873) - Link from "Recent Alerts" portlet to Alert should be from Date/Time Column
Summary: Link from "Recent Alerts" portlet to Alert should be from Date/Time Column
Alias: RHQ-1873
Product: RHQ Project
Classification: Other
Component: Core UI
Version: unspecified
Hardware: All
OS: All
medium vote
Target Milestone: ---
: ---
Assignee: Jay Shaughnessy
QA Contact: Jeff Weiss
URL: http://jira.rhq-project.org/browse/RH...
Depends On:
Blocks: rhq4
TreeView+ depends on / blocked
Reported: 2009-03-26 21:07 UTC by Jeff Weiss
Modified: 2014-11-09 22:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2013-09-02 07:18:17 UTC

Attachments (Terms of Use)

Description Jeff Weiss 2009-03-26 21:07:00 UTC
There are 3 columns in this portlet:

Resource Name,  	Alert Name,  	Date / Time

The first column is fine, but the 2nd column has links to the Alert, but since Alerts are named the same as the Alert Def, it's not clear which it links to.  If you have 5 Alerts from the same Def, you'll see 5 links with the same text and they all go to different places.

I suggest making the links in the 2nd column go to the Definition.  The 3rd column should be made into links that go to the Alert itself.  This would be more in line with other parts of the UI where Date/Time fields are links to the thing that happened at that Date/Time.

Comment 1 Red Hat Bugzilla 2009-11-10 20:48:32 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1873

Comment 2 wes hayutin 2010-02-16 17:09:55 UTC
mass add of key word FutureFeature to help track

Comment 3 Jay Shaughnessy 2011-02-11 22:16:24 UTC
if possible set name link to def and date to alert

Comment 4 Jay Shaughnessy 2011-02-15 14:36:55 UTC
Done. This change carries through to all of the AlertHistoryList views. Also, dbl click will bring you to the history detail as well.

Comment 5 Mike Foley 2011-05-02 12:54:48 UTC
verified RHQ 4.0 release candidate #1.

Comment 6 Heiko W. Rupp 2013-09-02 07:18:17 UTC
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.

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