Bug 1375192

Summary:	[RFE] Allow composite content views to be configured to always use the latest version available of constituent content views
Product:	Red Hat Satellite	Reporter:	Julio Entrena Perez <jentrena>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, jentrena
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-11 19:58:53 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:
Bug Depends On:
Bug Blocks:	260381

Description Julio Entrena Perez 2016-09-12 12:49:55 UTC

> 1. Proposed title of this feature request  
Allow configuring Composite Content Views to always use the latest version available of constituent Content Views.

> 3. What is the nature and description of the request?
When a new version of a CCV is published, it will use by default the same version of the constituent CVs as the last time.
User can, if desired, click on the second column "Version" for each constituent CV and change the version.

Customer is requesting that, in the pull-down that lists the versions for each constituent CV, an additional option named "Latest" is added and selectable.
When user selects "Latest" version for a constituent CV, every future publishing of the CCV will include the latest available version of that CV at that time.

> 4. Why does the customer need this? (List the business requirements here)  
Customer expects to end up with a significant number of CCVs.
Being able to change the default behaviour by configuring CCVs to use the latest version of some/all of their constituent CVs would dramatically improve their workflow.

> 5. How would the customer like to achieve this? (List the functional requirements here)  
In the "Content Views" --> "List/Remove" screen of a CCV, users can already change the version of the constituent CVs.
Customer is requesting that an additional option is added to the pull-down in the "Version" column for each constituent CV.
This additional option will be named "Latest" and selecting it will cause Satellite to always use the latest available version of that constituent CV whenver a new version of the CCV is published.

> 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
The "Latest" option is added to the list of versions for each constituent CV in CCVs.
Selecting "Latest" version results in Satellite always including the latest available version of that constituent CV when publishing a new version of the CCV.

> 7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
No, but there are other bugs related to this functionality:
- bug 1353616 [RFE] Provide option to automatically update Composite content view when a child content view is incrementally updated
- bug 1289055 [RFE] Out of date filter for Composite Content Views
- bug 1309569 [RFE] Composite Content View Web UI: show if "Latest" view is in use or if new version of content view available
- bug 1331576 [RFE] Button to move all subscribed Composite Content Views to the latest version of a Content View

> 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
As soon as possible, ideally Satellite 6.3.

> 9. Is the sales team involved in this request and do they have any additional input?  
No.
   
> 10. List any affected packages or components.  
Unknown.

> 11. Would the customer be able to assist in testing this functionality if implemented?  
Yes.