Bug 766808

Summary: RFE: Display existing changesets alongside their matching environments
Product: Red Hat Satellite Reporter: Og Maciel <omaciel>
Component: WebUIAssignee: Justin Sherrill <jsherril>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: mmccune
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-11 16:43:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Og Maciel 2011-12-12 16:22:48 UTC
Description of problem:

Basically, the current behavior when creating a new changeset is to move it to the Changesets History page once it gets successfully promoted. Being new to the web ui and katello itself, I felt that it was counter intuitive, as I expected to at find the changeset listed under the environment where it got promoted to. So, if I had created a new changeset named "Release 1" under the Locker environment and wanted to promote it to Base environment (Locker > Base):

* List Release 1 under Locker for my organization until I successfully promote it
* Once promoted, maybe we could show some type of information under the Locker environment stating how many changesets have been created for that environment, which would then take the user to the Changesets History page when clicked (BONUS: Filter changeset by Environment)
* Going to the Base environment would then show me Release 1

Version-Release number of selected component (if applicable):

katello-0.1.130-1.git.0.216c0d8.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mike McCune 2011-12-19 04:45:54 UTC
I like the BONUS hehe

Comment 3 Mike McCune 2013-08-16 18:24:32 UTC
getting rid of 6.0.0 version since that doesn't exist

Comment 4 Bryan Kearney 2014-03-11 16:43:31 UTC
Closing old bugs which are not relevant based on new UI and CLI