Bug 697579 - Status field is missing from both Resource op history detail view and group op history detail view
Summary: Status field is missing from both Resource op history detail view and group o...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0.Beta2
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq4
TreeView+ depends on / blocked
 
Reported: 2011-04-18 16:29 UTC by Ian Springer
Modified: 2013-08-06 00:39 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)
resource-op-details.png (40.17 KB, image/png)
2011-04-26 20:11 UTC, John Mazzitelli 		no flags Details
group-op-details.png (42.63 KB, image/jpeg)
2011-04-26 20:11 UTC, John Mazzitelli 		no flags Details
View All

Description Ian Springer 2011-04-18 16:29:27 UTC 
list views have Status field, but details views do not
Comment 1 John Mazzitelli 2011-04-26 20:10:53 UTC 
this is fixed from some commit last week. The group and resource operation details view now show a "Status" icon. See attached.
Comment 2 John Mazzitelli 2011-04-26 20:11:29 UTC 
Created attachment 495027 [details]
resource-op-details.png
Comment 3 John Mazzitelli 2011-04-26 20:11:50 UTC 
Created attachment 495028 [details]
group-op-details.png
Comment 4 Sunil Kondkar 2011-05-05 09:48:07 UTC 
Verified on rhq4 release build. (Version: 4.0.0 Build Number: db0c817)

Status field is displayed on Resource and group operation history detail view.

Marking as verified.
Comment 5 Corey Welton 2011-05-24 01:15:44 UTC 
Bookkeeping - closing bug - fixed in recent release.
Comment 6 Corey Welton 2011-05-24 01:15:45 UTC 
Bookkeeping - closing bug - fixed in recent release.
Comment 7 Corey Welton 2011-05-24 01:15:47 UTC 
Bookkeeping - closing bug - fixed in recent release.
Comment 8 Corey Welton 2011-05-24 01:15:56 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.