Bug 1389021 - [RFE] Container reports selector show 100's of non-container fields
Summary: [RFE] Container reports selector show 100's of non-container fields
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: unspecified
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: GA
: cfme-future
Assignee: John Hardy
QA Contact: Einat Pacifici
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 16:41 UTC by Mike Dahlgren
Modified: 2019-01-22 12:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-22 12:22:24 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)
Container_selection_1 (157.61 KB, image/png)
2016-10-26 16:41 UTC, Mike Dahlgren
no flags Details
Container_selection_2 (132.97 KB, image/png)
2016-10-26 16:41 UTC, Mike Dahlgren
no flags Details

Description Mike Dahlgren 2016-10-26 16:41:00 UTC
Created attachment 1214353 [details]
Container_selection_1

Description of problem:
When creating a report and choosing the "Configure Report Columns" the user is presented with hundreds of values that have no relationship to containers and it is difficult to find the valid fields.  

e.g. "Node.Computer Systems.Hardware.Network Adapters: File Name"

This is true for basing reports on "Containers, Container Images, and Container Services) 

*See screenshots


How reproducible:100%


Steps to Reproduce:
1. Go to Reports -> Configure -> "Add a new report"
2. Choose to "* Base the report on" "Container Images"
3. Attempt to find the appropriate fields.

Actual results:
Output shows hundreds of options that are not valid.

Expected results:
User would see the options that are appropriate for "Container Images"


Additional info: See attached

Comment 2 Mike Dahlgren 2016-10-26 16:41:43 UTC
Created attachment 1214354 [details]
Container_selection_2


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