Bug 661800 - Not all name column values generate a link to the detail view
Summary: Not all name column values generate a link to the detail view
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0.B02
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Ian Springer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-09 16:56 UTC by Jay Shaughnessy
Modified: 2013-08-06 00:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Jay Shaughnessy 2010-12-09 16:56:29 UTC
(11:40:05 AM) jshaughn: ips, did we ever complete broad coverage for the dbl-click/name link approach?
(11:40:52 AM) ips: jshaughn: i don't think so. we have double-click everywhere that uses TableSection
(11:41:29 AM) ips: but we probably need to go through and add the name links to all the pages that use TableSection
(11:42:05 AM) jshaughn: ok
(11:42:06 AM) ips: may be worth adding an abstract method in TableSection to force subclasses to provide a link
(11:43:12 AM) ips: protected getDetailsLink(int id) 
(11:43:45 AM) ips: actually the link will always be tableSectionsViewPath + "/" + id   right?
(11:44:15 AM) jshaughn: ips, I think so
(11:44:32 AM) ips: so maybe all that's needed would be protected abstract getLinkColumnFieldName()
(11:44:44 AM) ips: which could have the default impl: return "name";
(11:45:07 AM) jshaughn: ips, yeah, I think a base impl would cover most, if not all cases

Comment 1 Ian Springer 2010-12-09 21:27:33 UTC
Done - [master df6684a].

Comment 2 Corey Welton 2011-05-24 01:14:11 UTC
Bookkeeping - closing bug - fixed in recent release.

Comment 3 Corey Welton 2011-05-24 01:14:13 UTC
Bookkeeping - closing bug - fixed in recent release.

Comment 4 Corey Welton 2011-05-24 01:14:13 UTC
Bookkeeping - closing bug - fixed in recent release.


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