Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1509924 - Container Provider Advance settings need image inspector title
Summary: Container Provider Advance settings need image inspector title
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: User Experience
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: cfme-future
Assignee: Serena
QA Contact: Dave Johnson
Whiteboard: containers
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-06 10:55 UTC by brahmani
Modified: 2018-01-05 23:48 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-11-06 11:02:53 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
advance settings (deleted)
2017-11-06 10:55 UTC, brahmani
no flags Details

Description brahmani 2017-11-06 10:55:35 UTC
Created attachment 1348524 [details]
advance settings

Description of problem:
On Container Provider Advance settings it is not clear that the Proxy Settings are related to the Image Inspector settings.
I suggest to add, on Advance Tab, Title : "Image Inspector Options"
So user will know that the parameters under it related to Image Inspector

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Compute → containers → providers
2.Select provider check box → configuration → edit selected Containers provider
3.Settings → Advance →

Actual results:

Expected results:
Title : "Image Inspector Options" , and bellow the settings parameters.

Additional info:

Comment 2 RHEL Product and Program Management 2017-11-06 11:02:53 UTC
Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

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