Bug 2102202

Summary: [RFE]: After publishing a content view I should see all versions of the Content Views
Product: Red Hat Satellite Reporter: Taft Sanders <tasander>
Component: Content ViewsAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: msviriko, sajha
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Taft Sanders 2022-06-29 13:04:19 UTC
Description of problem:
As a user, publishing a content view will leave me on the page of the version of the content view that just finished publishing. While this provides confirmation that the new version was successfully published and what repository was included in it, it doesn't provide me any more context than this. If the version publish concluded and returned me back to the content view's version table list, I then can see the difference between the previous versions and the latest version to understand how many packages could be included in my client's next update.

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

How reproducible:
Every time

Steps to Reproduce:
1. Publish a content view
2. 
3.

Actual results:
Ends with the specific version shown after the publish

Expected results:
Viewing the table of all versions for the content view

Additional info:

Comment 3 Maria Svirikova 2023-04-11 12:24:58 UTC
It's more consistent to keep the behavior as it is. We do the same in creation flows.
But, I would suggest adding a "Compare versions" action to the kebab in the version detail page.

Comment 5 Brad Buckingham 2023-07-21 21:06:39 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.