Bug 1161645 - [RFE] Support publishing to multiple environments
Summary: [RFE] Support publishing to multiple environments
Keywords:
Status: CLOSED DUPLICATE of bug 1104346
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jameer Pathan
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2014-11-07 14:42 UTC by Justin Sherrill
Modified: 2022-10-10 13:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-05 20:04:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 5405 0 None None None 2016-04-22 16:34:05 UTC
Red Hat Issue Tracker SAT-13355 0 None None None 2022-10-10 13:00:40 UTC

Description Justin Sherrill 2014-11-07 14:42:47 UTC 
Description of problem:

Currently when publishing a new content view version we promote directly to library, we should let the user publish to any number of environments they wish as part of this step.

Version-Release number of selected component (if applicable):
6.0.4
Comment 1 RHEL Program Management 2014-11-07 14:42:59 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 4 David Davis 2014-12-05 17:07:12 UTC 
You can already promote directly to an env (and bypass lifecycle restrictions) using force so I retitled this. Linking it up with the redmine issue.
Comment 5 Bryan Kearney 2015-08-25 18:32:34 UTC 
Upstream bug component is Content Views
Comment 6 Bryan Kearney 2016-07-08 20:29:44 UTC 
Per 6.3 planning, moving out non acked bugs to the backlog
Comment 8 Brad Buckingham 2016-08-05 20:04:32 UTC 

*** This bug has been marked as a duplicate of bug 1104346 ***
Note You need to log in before you can comment on or make changes to this bug.