Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRussell Dickenson
2017-01-13 03:14:07 UTC
Description of problem: When making changes to a Content View, the user cannot know in advance how many packages and/or errata match the criteria. This is important because it provides no benefit if the criteria are incorrect. At the moment the only means of doing this is to publish the Content View and check the Content column of the table on the Content View's "Versions" tab. Using that method is inefficient because it can take several minutes for a Content View to be published. If getting a Content View's criteria correct requires a cycle of "change, save, publish, check, and repeat", that is very inefficient.
How reproducible: Always.
Steps to Reproduce:
1. Open the Satellite web UI, and navigate to Content > Content Views.
2. Make a change to a Content View's criteria, and save the changes.
Actual results: There is no means of confirming how many packages match the Content View, except for saving and publishing it.
Expected results: There is an option to "preview" the number of packages which would match the Content View's edited and saved, but not yet published, criteria.