Bug 1126129 - [RFE] it should be possible to remove Content View versions without promotion
Summary: [RFE] it should be possible to remove Content View versions without promotion
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Views
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-02 06:43 UTC by Sebastian Hetze
Modified: 2016-08-04 19:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-04 19:28:25 UTC


Attachments (Terms of Use)

Description Sebastian Hetze 2014-08-02 06:43:46 UTC
Currently, a Content View version can only be removed if it is promoted to an environment.

This is not intuitive and does not follow the natural workflow.

When creating a new Content View version it is automatically promoted to the Library environment, thereby replacing the previous version. Further promotions do again oust the previous version, leaving the old version unused eventually.

These unused old versions pile up and can only be removed by promoting them to Library again one by one.

Given the requirement of being unused before removing, the necessity of promotion before removing is even dangerous since exactly this makes the old version available again...

Comment 1 RHEL Product and Program Management 2014-08-02 07:03:41 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Brad Buckingham 2016-08-04 19:28:25 UTC
The restriction described no longer exists.  In Satellite 6.2 (and 6.1), it is possible to remove a content view version that is not currently associated with a Lifecycle Environment.  

Closing this bugzilla; however, please re-open this one or create a new one, if issues additional issues are identified.  Thanks!


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