Project

General

Profile

Feature #15950

Add ability to publish "latest version" in a composite view

Added by Partha Aji almost 5 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Content Views
Target version:
Difficulty:
medium
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Consider a composite content view with multiple component views

As a user I would like the ability to always select the "latest version" of a component view every time I publish it


Related issues

Blocks Katello - Feature #15965: Would like a hammer cli to add components to cvClosed2016-08-03

Associated revisions

Revision 5582db4f (diff)
Added by Partha Aji over 4 years ago

Fixes #15950 - CV Composite accepts latest version

This commit enables one to add the "latest" content view version to a
composite content view.
For example
If you had cv1 with versions 1,2,3 and cv2 with versions 1,2 and a new
composite content view ccv, you can now do the following operations
1) Add a cv component to ccv and say
"Always pick the latest version of the cv2" when ccv is published
2) Remove cv components of ccv individually
3) Controller calls for Content View components
4) UI Bindings for the same

History

#1 Updated by Partha Aji almost 5 years ago

  • Blocks Feature #15965: Would like a hammer cli to add components to cv added

#2 Updated by Justin Sherrill over 4 years ago

  • Category set to Content Views
  • Legacy Backlogs Release (now unused) set to 162
  • Difficulty set to medium

#3 Updated by John Mitsch over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 162 to 114

#4 Updated by Brad Buckingham over 4 years ago

  • Status changed from New to Assigned

Partha, I am moving this to assigned, since you mentioned that you are actively working on it.

#5 Updated by Brad Buckingham over 4 years ago

  • Bugzilla link set to 1177766

Associating a bugzilla to this issue that provides more description of what other users are requesting. When solving this issue, please review it and any associated duplicates. Thanks!

#6 Updated by The Foreman Bot over 4 years ago

  • Status changed from Assigned to Ready For Testing
  • Legacy Backlogs Release (now unused) deleted (114)
  • Pull request https://github.com/Katello/katello/pull/6416 added

#7 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) set to 188

#8 Updated by Partha Aji over 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF