Bug 1305173

Summary:	[RFE] Display heirarchy for RHEV sub-templates
Product:	Red Hat CloudForms Management Engine	Reporter:	Colin Arnott <carnott>
Component:	Providers	Assignee:	John Hardy <jhardy>
Status:	CLOSED WONTFIX	QA Contact:	Ilanit Stein <istein>
Severity:	low	Docs Contact:
Priority:	medium
Version:	5.5.0	CC:	benglish, hkataria, istein, jfrey, jhardy, jocarter, mpovolny, obarenbo, simaishi
Target Milestone:	GA	Keywords:	FutureFeature, RFE
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	rhev
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-18 13:27:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Colin Arnott 2016-02-05 22:12:29 UTC

Description of problem:
In CFME, the RHEV sub-templates are named the same as the master template, in such a way that you cannot distinguish between them. There should be a field for sub-template version, or the version should be appended to the name. Currently, the master template and any sub-templates show as the master template name only.

How reproducible:
view RHEV sub-templates in CFME

Steps to Reproduce:
1. go to the catalog
2. look at RHEV sub-templates

Actual results:
all sub-templates are named the same as the master template

Expected results:
there should be a field for sub-template version, or the version should be appended to the name

Comment 5 Josh Carter 2018-09-18 13:27:55 UTC

Dear customer, 

The CloudForms team is reviewing the current CloudForms RFE(Request for Enhancement) backlog in order to improve our responsiveness to customers. We are closing any requests for versions no longer within full support(link below to the lifecycle) or that do not have a clear spot on the product roadmap. We are committing to better management of the backlog as we move forward. If you have an RFE that you still have a strong business case for, please open a new BZ against the currently supported version 4.6.

Lifecycle page: https://access.redhat.com/support/policy/updates/cloudforms

If you have any concerns about this, please let us know.

Thanks and regards!”