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:
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.
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.